FIspace Project Final Report - Europa · FIspace Project Final Report WP 100 Project Acronym &...

Deliverable D100.8/D100.9

FIspace Project Final Report

WP 100

Project Acronym & Number: FIspace – 604 123

Project Title: FIspace: Future Internet Business Collaboration Networks in Agri-Food, Transport and Logistics

Funding Scheme: Collaborative Project - Large-scale Integrated Project (IP)

Date of latest version of Annex 1: 17.03.2015

Start date of the project: 01.04.2013

Duration: 30

Status: Final

Editors: Harald Sundmaeker, Andreas Metzger, Michael Zahlmann

Contributors: All FIspace Beneficiaries

Document Identifier: FIspace-D100.8-9-ProjectFinalReport-V08.docx

Date: 11.11.2015

Revision: 08

Project website address: http://www.FIspace.eu

http://www.fispace.eu/

FIspace 11.11.2015

FIspace-D100.8-9-ProjectFinalReport-V08.docx of 130

The FIspace Project

Leveraging on outcomes of two complementary FIWARE Phase 1 use case projects (FInest & SmartA-griFood), aim of FIspace was to pioneer towards fundamental changes on how collaborative business networks will work in the future. FIspace developed a multi-domain Business Collaboration Space (short: FIspace) that employs FIWARE technologies for enabling seamless collaboration in open, cross-organizational business networks, establish eight working Experimentation Sites in Europe where Pilot Applications are tested in Early Trials for Agri-Food, Transport & Logistics and prepare for industrial up-take by engaging with players & associations from relevant industry sectors and IT industry.

Project Summary

As a use case project in Phase 2 of FIWARE, FIspace aimed at developing and validating novel Future-Internet-enabled solutions to address the pressing challenges arising in collaborative business networks, focussing on use cases from the Agri-Food, Transport and Logistics industries. FIspace focused on ex-ploiting, incorporating and validating the FIWARE Generic Enablers with the aim of realising an extensible collaboration service for business networks together with a set of innovative test applications that allow for radical improvements in how networked businesses can work in the future. Those solutions were demonstrated and tested through early trials on experimentation sites across Europe. The project results are open to the FIWARE program participants and the general public. Especially the pro-active engage-ment of larger user communities and external solution providers helped to initiate the industrial uptake by FIWARE Phase 3 software developers.

Project Consortium

DLO; Netherlands Kühne + Nagel; Switzerland

ATB Bremen; Germany University Duisburg Essen; Germany

IBM; Israel ATOS; Spain

KocSistem; Turkey The Open Group; United Kingdom

Aston University; United Kingdom CentMa; Germany

ENoLL; Belgium iMinds; Belgium

KTBL; Germany Marintek; Norway

NKUA; Greece University Politecnica Madrid; Spain

Wageningen University; Netherlands Arcelik; Turkey

PlusFresc; Spain EuroPoolSystem; Germany

FloriCode; Netherlands GS1 Germany; Germany

Kverneland; Netherlands Mieloo & Alexander; Netherlands

North Sea Container Line; Norway OPEKEPE; Greece

LimeTri; Netherlands Innovators; Greece

BO-MO; Slovenia CIT; Spain

MOBICS; Greece SDZ; Germany

Fraunhofer IML; Germany Snoopmedia; Germany

Q-ray; Netherlands EECC; Germany

FINCONS; Italy CBT; Spain

More Information

Harald Sundmaeker (coordinator)

ATB Bremen GmbH

Wiener Str. 1

D-28359 Bremen; Germany

e-mail: [email protected]

phone: +49 421 220920

www.FIspace.eu Twitter.com/FIspace_eu


https://twitter.com/FIspace_eu

FIspace 11.11.2015


Dissemination Level

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) X

CO Confidential, only for members of the consortium (including the Commission Services)

Document Summary

This final report presents an overview of the FIspace project. It compiles the main results that were elabo-rated within its project duration and highlights the main outcomes that are representing the baseline for future uptake of technology and commercialisation of the FIspace platform.

This document shall also facilitate an understanding of the FIspace results and help external parties to learn from the achievements as well as to promote a reuse of the FIspace achievements.

However, this document is compiling both parts – the public as well as the restricted part. Only the public part will be made available to an external audience.

FIspace 11.11.2015


Abbreviations

ACSI Artifact-Centric Service Interop-eration

AIL Administrative Intermediate Layer

API Application Programming Inter-face

App Software Application

B2B Business to Business

BCM Business Collaboration Module

CSB Cloud Service Bus

D Deliverable

DoW Description of Work

EC European Commission

e.g. Exempli gratia = for example

EPC Electronic Product Code

EPCIS EPC Information System

EPM Event Processing Module

EU European Union

FFV Fresh Fruits and Vegetables

FIA Future Internet Assembly

FI PPP Future Internet Public Private Partnership

FP7 Framework Programme 7

GA Grant Agreement

GE Generic Enabler

GSM Guards, Stages, and Milestones

GTIN Global Trade Item Number

ICT Information and Communication Technology

IoT Internet of Things

IT Information Technology

i.e. id est = that is to say

IP Intellectual Property

IPR Intellectual Property Rights

KPI Key Performance Indicator

LSP Logistics Service Providers

M Month

Mgt Management

MIP Meat Information Provenance

QoS Quality of Service

RTD Research and Technological Development

SDI System and Data Integration

SDK Software Development Kit

SLA Service Level Agreement

SME Small and Medium Sized Enter-prise

SPT Security, Privacy and Trust

SSO Single Sign-On

ST Sub-Task

T Task

TIC Tailored Information for Con-sumers

TRL Technology Readiness Level

WP Work Package

FIspace 11.11.2015


Table of Contents

1 Introduction ....................................................................................................................................... 9

1.1 Executive Summary .................................................................................................................. 9

1.2 Contents of the Final Report ................................................................................................... 10

2 FIspace – an Overview ................................................................................................................... 11

2.1 FIspace Platform High Level Architecture .............................................................................. 11

2.2 Extensibility of FIspace ........................................................................................................... 13

2.3 FIspace as the intermediary of multiple two-sided markets ................................................... 13

2.4 FIspace Trials and Apps ......................................................................................................... 14

2.4.1 Farming in the Cloud .............................................................................................................. 15

2.4.2 Intelligent Perishable Goods Logistics ................................................................................... 15

2.4.3 Smart Distribution and Consumption ...................................................................................... 15

2.5 Project Public Website and Contact Details ........................................................................... 15

3 Project Results ................................................................................................................................ 16

3.1 FIspace – A Multi-sided B2B Platform .................................................................................... 16

3.1.1 Business Impact ..................................................................................................................... 16

3.1.2 Main Features and Building Blocks ........................................................................................ 17

3.2 FIspace Operation Model – Illustrative Example .................................................................... 20

3.2.1 Sample Scenario: Spraying Advice ........................................................................................ 20

3.2.2 Illustration of FIspace Apps and Overall Operational Model .................................................. 21

3.3 The FIspace Platform Main Components ............................................................................... 24

3.3.1 FIspace Front End Component .............................................................................................. 24

3.3.2 FIspace Store Component ...................................................................................................... 25

3.3.3 Business to business (B2B) component ................................................................................. 28

3.3.4 System and Data Integration (SDI) Component ..................................................................... 31

3.3.5 Operating Environment Component ....................................................................................... 32

3.3.6 Security, Privacy and Trust Component ................................................................................. 34

3.3.7 Software Development Kit ...................................................................................................... 35

3.3.8 FIspace Features – Release V0.16.0 ..................................................................................... 37

3.4 Application Potentials – FIspace Pilots in Detail .................................................................... 43

3.4.1 Trial 1 – Crop Protection Information Sharing ........................................................................ 43

3.4.2 Trial 2 – Greenhouse Management & Control........................................................................ 45

3.4.3 Trial 3 – Fish Distribution and (Re-) Planning ........................................................................ 46

3.4.4 Trial 4 – Fruit & Vegetables Quality Assurance..................................................................... 48

3.4.5 Trial 5 – Flowers and Plants Supply Chain Monitoring .......................................................... 49

3.4.6 Trial 6 – Meat Information Provenance .................................................................................. 50

3.4.7 Trial 7 – Import & Export of Consumer Goods ....................................................................... 52

3.4.8 Trial 8 – Tailored Information for Consumers ......................................................................... 53

FIspace 11.11.2015


4 Offering and Support for FIWARE Phase 3 Projects ................................................................... 56

4.1 Description of technical support ............................................................................................. 56

4.2 Bug fixing ................................................................................................................................ 56

4.3 Communication of Platform Status ......................................................................................... 57

4.4 Operational Hosting of the Platform ....................................................................................... 57

4.5 Assignment of User Roles ...................................................................................................... 57

4.6 Registering Messages for new capability types ..................................................................... 57

4.7 Deployment/removal of Business Processes and CEP Patterns ........................................... 58

5 Commercialisation Prospects ....................................................................................................... 59

5.1 The FIspace Usage Model ..................................................................................................... 59

5.1.1 Main FIspace Processes ........................................................................................................ 59

5.1.2 Principal User Groups and Workflows .................................................................................... 60

5.2 The FIspace Business Model ................................................................................................. 61

5.2.1 FIspace Business Model CANVAS ........................................................................................ 61

5.2.2 FIspace Generic Value Network ............................................................................................. 65

5.2.3 Basic Business Model Scenarios ........................................................................................... 67

5.3 Potential Constraints .............................................................................................................. 70

5.3.1 The challenge of financial liability for failure of the platform ................................................... 70

5.3.2 The challenge of jurisdiction ................................................................................................... 71

5.3.3 The challenge of flexibility vs. legal constraints ...................................................................... 71

5.3.4 Conclusion about Potential Constraints ................................................................................. 71

5.4 The FIspace Foundation – Next Steps towards Commercialisation ...................................... 72

6 Policy Recommendations .............................................................................................................. 75

6.1 Recommendations for Private Stakeholders .......................................................................... 75

6.2 Recommendations for Public Stakeholders ........................................................................... 76

7 Innovations ...................................................................................................................................... 78

7.1 App Innovations ...................................................................................................................... 78

7.2 Platform Innovations ............................................................................................................... 81

7.3 Infrastructure Innovations ....................................................................................................... 82

7.4 Process Innovations ............................................................................................................... 82

7.5 Individual Innovations ............................................................................................................. 84

7.5.1 A1 – Improved Shopping Experience App ............................................................................. 84

7.5.2 A2 – Fresh Food Transparency Apps .................................................................................... 85

7.5.3 A3 – Import and export of consumer goods Apps .................................................................. 86

7.5.4 A4 – CargoSwApp .................................................................................................................. 87

7.5.5 A5 – Botanic Trading Information App ................................................................................... 88

7.5.6 A6 – RISKMAN App - Risk Management in the Distribution of Fresh Food and Vegetables 89

7.5.7 A7 – BizSLAM App – Business SLA Management ................................................................ 89

7.5.8 A8 – Bad Weather Warning App ............................................................................................ 90

FIspace 11.11.2015


7.5.9 A9 – Traffic Light App ............................................................................................................. 91

7.5.10 A10 – BOXMAN ...................................................................................................................... 92

7.5.11 A11 – Product: PIA (Product Information App) ....................................................................... 93

7.5.12 A12 – Tailored Information for Consumers Initial App (TIC) .................................................. 94

7.5.13 P1 – FIspace Studio ............................................................................................................... 95

7.5.14 P2 – Business process collaboration enhanced with complex event driven capabilities ....... 96

7.5.15 P3 – Ygg: Capability-driven Cross-Organizational Business Collaboration ........................... 97

7.5.16 P4 – Composite Service Bus .................................................................................................. 98

7.5.17 I1 – Low Cost Wireless Sensor Network based on Open Hardware ...................................... 99

7.5.18 I2 – Real-Time Cargo Volume Recognition .......................................................................... 100

7.5.19 X1 – Linked Pedigrees ......................................................................................................... 101

7.5.20 X2 – Floriculture logistic label and business rules................................................................ 102

7.5.21 X3 – Predictive Transport Process Monitoring ..................................................................... 103

8 Section A (public) – Use and Dissemination of Foreground .................................................... 104

8.1 Listing of Dissemination Activities ........................................................................................ 104

9 Section B: Confidential Information ........................................................................................... 122

9.1 Part B1 – Applications for Patents, Trademarks, Registered Designs etc. .......................... 122

9.2 Part B2 – Report on societal implications ............................................................................. 122

FIspace 11.11.2015


List of Figures

Figure 1: The FIspace platform for collaborative business networks. ..................................................... 9

Figure 2: FIspace Platform High Level Architecture .............................................................................. 11

Figure 3: FIspace Extension Mechanisms ............................................................................................. 13

Figure 4: Stylised representation of the multiple two-sided markets in FIspace ................................... 14

Figure 5: Motivation & Cross-Domain Requirements ............................................................................ 16

Figure 6: Main aspects of the FIspace platform components in relation to the high-level conceptual architecture. ......................................................................................................... 18

Figure 7: Sample Scenario 'Spraying Advice' - AS IS Overview ........................................................... 20

Figure 8: Sample Scenario 'Spraying Advice' - TO BE Overview ......................................................... 21

Figure 9: FIspace App ‘Get Spraying Advice‘ – Illustrative Design ....................................................... 21

Figure 10: Illustration of FIspace Overall Operational Model .................................................................. 22

Figure 11: Overview of User Front-End component ................................................................................ 24

Figure 12: FIspace Store Overview ......................................................................................................... 26

Figure 13: Store – High level composite architecture .............................................................................. 27

Figure 14: High level composite architecture for EPM ............................................................................ 30

Figure 15: High level composite architecture for BCM ............................................................................ 30

Figure 16: SDI interaction model overview .............................................................................................. 31

Figure 17: SDI high-level architecture. .................................................................................................... 32

Figure 18: CSB high level architecture .................................................................................................... 34

Figure 19: SPT high-level architecture .................................................................................................... 35

Figure 20: FIspace use case trial experimentation sites ......................................................................... 43

Figure 21: Layout Crop Protection Information Sharing Trial .................................................................. 44

Figure 22: Greenhouse Management & Control Trial overview .............................................................. 45

Figure 23: Layout of Fish Distribution and (Re-)Planning Trial ............................................................... 47

Figure 24: Principal organization of the FFV food chain. ......................................................................... 48

Figure 25: Layout of Flowers and Plants Supply Chain Monitoring Trial ................................................. 49

Figure 26: Reference architecture with the core parts to be implemented and tested in FIspace’s MIP trial. ................................................................................................................. 51

Figure 27: Layout of Import and Export of Consumer Goods Trial .......................................................... 52

Figure 28: Main FIspace Usage Processes ............................................................................................. 59

Figure 29: FIspace Generic Value Network ............................................................................................. 65

Figure 30: Main partners in the value network mapped to their roles ..................................................... 66

Figure 31: Commercial development of the FIspace platform based on a foundation. ........................... 72

List of Tables

Table 1: FIspace features by target audience – Release V0.16.0 ....................................................... 37

Table 2: FIspace features by FIspace Components – Release V0.16.0 .............................................. 40

Table 3: Example „Traffic Light“ app information ................................................................................. 54

Table 4: FIspace merged canvas ......................................................................................................... 61

Table 5: Comparison of business model scenarios .............................................................................. 69

Table 6: FIspace dissemination activities in the second/ final reporting period and beyond. ............ 105

FIspace 11.11.2015


1 Introduction

1.1 Executive Summary

As a use case project in the 2nd

FIWARE phase, FIspace aimed at developing and validating novel Fu-ture-Internet-enabled solutions to address the pressing challenges arising in collaborative business net-works, focussing on use cases from the Agri-Food, Transport and Logistics industries. FIspace focused on exploiting, incorporating and validating FIWARE Generic Enablers with the aim of realising an extensi-ble collaboration service for business networks together with a set of innovative test applications that allow for radical improvements in how networked businesses work in the future.

These solutions were demonstrated and tested through early trials on experimentation sites across Eu-rope. The project results are open to the FIWARE program and most of them to the general public. The pro-active engagement of larger user communities and involvement of external solution providers was addressed to foster the innovation and industrial uptake that is taking place in the 3

rd phase of FIWARE.

FIspace lays the foundation for realizing the vision and prepares for large-scale expansion, complying with the objectives and expected results of the FIWARE phase 2 use case projects. To achieve these outcomes the project focused on the following four primary work areas, for which the main concepts and approach are outlined below:

1. Implement an experimental FIspace platform as an open and extensible Software-as-a-Service solution along with an initial set of applications for B2B collaboration, utilizing the FI-WARE Generic Enablers.

2. Establishing Experimentation Sites across Europe where the applications were tested in early trials representing the Agri-Food and the Transport and Logistics domains.

3. Providing a working Experimentation Environment for conducting early and large-scale tri-als for FIWARE enabled B2B collaboration in several domains, and

4. Preparing an industrial uptake and innovation enablement by pro-active engagement of stakeholders and associations from relevant industry sectors and the IT industry.

The FIspace platform instance is available and offered to a public target audience (www.fispace.eu) – a cloud-based platform for collaborative business networks (see Figure 1).

Figure 1: The FIspace platform for collaborative business networks.

FIspace is built upon key components, which serve as environment to offer and host applications for B2B collaboration. Such applications are characterized by simple, lightweight functionalities, while this collabo-ration is supported by a B2B collaboration core that handles object states, event handling, (re-)planning processes, etc. At the same time system integration, security, messaging and a related user interface is offered. The 8 FIspace trials were experimenting on this platform basis as well as verified and validated


FIspace 11.11.2015


their applications (www.fispace.eu/apps.html) based on the FIspace architectural principles. Furthermore, they were providing real-world scenarios, guiding the way to implement FIWARE based solutions and how to take advantage from the available FIspace results.

1.2 Contents of the Final Report

The FIspace final project report is providing a summary of the results and findings that were elaborated in the scope of FIspace. The following chapter 2 is presenting a general overview, to facilitate an under-standing of what was elaborated in the scope of the FIWARE use case project FIspace.

At the same time, this report compiles the outcomes of the different project work packages that were structured with respect to the main fields of expertise involved in FIspace:

Software development of the FIspace SaaS platform as well as integration, hosting and experimenta-tion as baseline for project internal work as well as for providing FIspace to external developers and end-users – see section 3.3

Analysis of end-user requirements and validation of technology in so called FIspace pilots addressing different business domains in agri-food and transport and logistics – see section 3.4

Development of software applications that can be run on the FIspace platform, while they can also be combined with each other by using the B2B collaboration core of the platform – see also section 3.4

The main principles of the FIspace platform are shortly introduced in section 3.1, while an illustrative ex-ample explains the usage of FIspace in section 3.2.

To learn about the features of FIspace and its usage in concrete application scenarios, end-users and application developers can experiment with a running FIspace platform instance that is hosted and main-tained by the FIspace project consortium also after the end of the FIspace project itself. However, to as-sure availability of the platform and to provide required bug-fixing, FIspace partners prepared a related approach that is presented in chapter 4.

On top of that, the FIspace partners were carefully analysing the business potentials of the FIspace plat-form. Potential usage and business models were analysed and served as baseline when establishing the FIspace foundation in August 2015 that shall coordinate the commercial follow-up after the end of the EC funded work in the FIspace project. Further details are presented in chapter 5.

However, as noted in many of the FIspace reports, the agriculture, food and logistics sectors have certain unique characteristics that make them substantively different from other industrial sectors (such as the automotive, plastics or electronics sectors). Food and agriculture are highly regulated sectors (logistics is somewhat less so) and thus government policy plays a more substantive role than in other sectors in defining the playing field for stakeholders in the market, and consequently the opportunities for an ICT platform such as FIspace. Therefore, FIspace was analysing of what proposals could be made for policy to change. Chapter 6 presents the recommendations, elaborated by the FIspace consortium.

As part of the FIspace project, many individual innovations have been made. Many of those were essen-tial to delivering the FIspace platform, others were triggered by the FIspace platform itself. Chapter 7 de-scribes these individual innovations of the FIspace project as reported by the project members.

Chapter 8 is listing the different dissemination activities that were accomplished by the FIspace consorti-um. It shall serve as a summary of material that can be used by future activities, also helping to under-stand on where to access related materials. Of course, the FIspace website remains the main entry point when searching for the most recent information.

Chapter 9 is concluding with the report on societal implications.

http://www.fispace.eu/apps.html

FIspace 11.11.2015


2 FIspace – an Overview

FIspace delivered an Open Business Collaboration Space that enables the seamless collaboration in open cross-domain business networks and represents the baseline for establishing an ecosystem of us-ers from various industrial sectors as well as IT solution providers.

FIspace provides a complete platform, which facilitates a focus on functionalities and business interoper-ability. It disburdens solution providers from realising complex server side functionalities as well as ease the application development. For being able to do so, FIspace developed a foundation of reusable com-mon functionalities that are making basic operations transparent to developers. On top of that, developers need not to navigate individually, since they are accompanied by the FIspace Studio that is an Integrated Development Environment with a complete software development kit (SDK), tutorials, HOWTO, utilities, examples and knowledge bases area.

The FIspace user itself has a personalised page to easily select and access his favourite applications, notifications, contacts, etc. to improve business processes with other organisations. The following Figure 2 presents the FIspace high level architecture.

Figure 2: FIspace Platform High Level Architecture

2.1 FIspace Platform High Level Architecture

The FIspace Platform High Level Architecture is described in the following, explaining the key features that are incorporated.

FIspace Front End

The FIspace Front-End builds the main access point for end-users of the FIspace platform, whereas this is not limited to the user interface, with which the end-users directly interact, but also encompasses serv-er-side components that are closely related to the user interface. Through the integration of external user interfaces (e.g., from the store, externally developed Apps or other external providers), the Front-End facilitates an ‘all you need in one place’ user experience and creates a central access point. To support the diversity of FIspace users and devices the Front-End user interface adapts to specific needs. This allows ubiquitous access and is enabled by backend components of the Front-End. Beyond the adapta-tion to different devices, the Front-End also supports the configuration of the user interface. This allows the interface personalization in order to address specific user needs or enable custom brandings for com-panies. The Front-End also enables users to create relations to business partners to facilitate the com-munication among them (comparable to modern social networks).

FIspace 11.11.2015


FIspace Store

The FIspace Store provides the tool-supported infrastructure for providing, finding, and purchasing FIspace Apps that provide re-usable IT-solutions for seamless business collaboration and can be used and combined for the individual needs of End-Users.

FIspace B2B

The FIspace B2B component enables the orchestration of workflows, also enabling different stakeholders to interact in the scope of their business processes. The FIspace B2B is based on the entity-centric ap-proach

FIspace System & Data Integration

The FIspace System & Data Integration module allows an integration and continued usage of existing legacy and business systems as well as the integration of external systems and services, including sup-port for:

Connecting business and legacy systems used by individual users by means of tool-supported mech-anisms to allow an easy creation of adapters to business and legacy systems, as well as defining a set of standard channel types

Handling heterogeneous data by means of API for data mediation

Connecting external Systems and Services (e.g., IoT systems, 3rd party and public services) by means of APIs for importing / exporting data from connected business & legacy systems into the FIspace.

FIspace Development Toolkit

The Development Toolkit provides support for the business-specific extension and configuration of FIspace, particularly for:

App Developers to support the development and provisioning of Apps in accordance to the technical governance and procedures of FIspace

Business IT Experts to support the modelling and configuration of B2B workflows, to customize and extend FIspace to the individual needs of End-Users

There are also some common modules to ensure security and privacy related aspects as well as a place to provide an operating environment to run all modules. However, those components are transparent in its usage for external application developers or end-users.

FIspace 11.11.2015


2.2 Extensibility of FIspace

FIspace is an extensible Software-as-a-Service (SaaS) platform to support B2B collaboration. The two basic extension mechanisms supported by FIspace are indicated in Figure 3.

Figure 3: FIspace Extension Mechanisms

Extensibility of the platform is achieved by (1) addition of functionality through Apps, (2) configuration of the platform to support and control collaborative B2B workflows, which can orchestrate App functionalities as well as services provided by external business/legacy and IoT systems.

2.3 FIspace as the intermediary of multiple two-sided markets

While there are many stakeholders put in the spotlight in different circumstances and scenarios, in its core functionality, FIspace addresses issues and challenges that enable business collaboration between industry partners (enhanced) by the provision of apps. The platform is thus in the position of an interme-diary on multiple two-sided markets. The first two-sided market contains the app developers vs. business users. The second contains the business users as buyers and sellers. This is the case since functionali-ties such as searching for other businesses can be done on the platform itself.

However, the platform’s own functionalities are strictly focused, while enhanced by the provision of apps. These apps that are developed and hosted on the platform, might equally mediate business users on two sides of a market (with possible expansion to even more sides, such as advertisers). To illustrate this, a stylised representation using the example of shippers and logistics service providers (LSP) is given in Figure 4. The markets are represented by the yellow half circles, each connecting two parties.

FIspace 11.11.2015


Figure 4: Stylised representation of the multiple two-sided markets in FIspace

The weight of one side of the market can also define the attractiveness for the other side of the market (inter-group network effects). An innovation that is well adopted and has gained numerous adherents represents an asset for the platform with a certain control over this market side. Characteristics of this effect of two-sided markets can, for example, be translated for FIspace as following: the more LSPs are on the platform, the more options for the food producer and the more value to join.

FIspace will be positioned as a platform intermediating (or supporting apps to intermediate) multiple two-sided markets. These are business users as buyers and sellers. For the current project, these business users are situated in the transport, logistics and agri-food sector. The market is characterised by (mainly inter-group) network externalities where the rate of adoption of the platform on one side of the market defines the attractiveness for the other side to join.

2.4 FIspace Trials and Apps

In the scope of the FIspace project, trials were using the features provided by FIspace to run the applica-tions they have defined. FIspace partners developed a set of application that provide diverse business and/or domain-specific capabilities exploiting the features and envisioned future support for business collaboration. Those Apps are also supporting tasks of the specific use case scenarios. For that purpose even additional software developing partners were involved via an open call to specifically focus on trial specific application development. The realization of the trial-specific Apps was based upon the consoli-dated conceptual design of the FIspace platform and accomplishing the definition of mixed use case sce-narios and related cross-domain trial experiments.

The FIspace project established working experimentation infrastructures across Europe where FIspace pilot applications for selected real-world business scenarios from the Agri-Food and the Transport and Logistics sectors were developed and tested. These trials leverage and extend the work performed in FIWARE Phase I, in particular from the use case projects SmartAgriFood and FInest.

FIspace 11.11.2015


2.4.1 Farming in the Cloud

The “Farming in the Cloud” task addressed food production issues at the farm level and covers two use case trials:

Crop Protection Information Sharing: use of field sensor and satellite data to intelligently manage the application of pesticides for maximum crop protection

Greenhouse Management & Control: use of sensors to monitor key growth factors (UV radiation, moisture and humidity, soil conditions, etc.) and to feedback data to control systems to modify the growth environment for maximum yield and optimal quality

2.4.2 Intelligent Perishable Goods Logistics

The “Intelligent Perishable Goods Logistics” task addressed monitoring and environmental management issues of perishable goods as they flow through their supply chains so that waste is minimized and shelf life maximized covering three use case trials:

Fish Distribution and (Re-)Planning: focuses on the planning of logistics and transport activities, including transport order creation, transport demand (re)planning and distribution (re)scheduling

Fresh Fruit and Vegetables Quality Assurance: looks at the management of deviations (transports, products) that affect the distribution process for fresh fruit and vegetables (transport plan, food quality issues), either deviation from the plan or other external events requiring re-planning.

Flowers and Plants Supply Chain Monitoring: the monitoring and communication of transport and logistics activities focusing on tracking and tracing of shipments, assets and cargo, including quality conditions and simulated shelf life. Focus is with Cargo and Asset Quality Tracking (“intelligent cargo”), Shipment Tracking (“intelligent shipment”) and lifecycle information tracking of cargo characteristics/Cargo Integration along the chain.

2.4.3 Smart Distribution and Consumption

The “Smart Distribution and Consumption” is about helping consumers to obtain better information on the goods they purchase, and producers to better control the flow of their goods to the consumer, covering three use case trials:

Meat Information Provenance: ensuring that consumers, regulators and meat supply chain participants all have accurate information concerning where a meat product originated (production farm) and how it was affected by its distribu-tion (quality assurance).

Import and Export of Consumer Goods: the intelligent management of inbound materials to a production site and the smart distribution of fin-ished goods to consumers.

Tailored Information for Consumers: the provisioning of accurate information to individual consumer’s needs and feedback of this infor-mation to the producers

2.5 Project Public Website and Contact Details

Harald Sundmaeker (coordinator)

ATB Bremen GmbH

Wiener Str. 1

D-28359 Bremen; Germany

e-mail: [email protected]

phone: +49 421 220920

www.FIspace.eu Twitter.com/FIspace_eu


https://twitter.com/FIspace_eu

FIspace 11.11.2015


3 Project Results

3.1 FIspace – A Multi-sided B2B Platform

Modern business networks tend to be highly distributed inter-organizational entities spanning country boundaries composed of business partners who have limited insights into the overall network and who are only focused on optimizing their own small part of the value chain. Current ICT services generally support this limited network focus, and thus provide only basic support for inter-organizational data and process integration. This means that complex inter-organizational collaboration activities today must be accomplished through manual efforts.

Technology advancements are also placing increasing strains on existing ICT systems. New technologies for gathering data on field activities, such as new sensor technologies, scanners, and RFID, are creating data collection, distribution and management problems for existing Internet technology. Sharing of these data is also problematic as the requirements for privacy and security of these types of data are poorly supported by existing Internet services.

The lack of robust inter-organizational integration and collaboration systems hampers business efficiency and optimization for all parties involved in the planning and execution of multi-organization value chain activities: customer requirements for end-to-end tracking and tracing must be satisfied through combina-tions of human inputs and interventions, heterogeneous information from incompatible ICT systems cre-ate barriers to interoperability between network partner systems, and the end-to-end coordination of op-erational planning and execution activities requires extensive manual effort making network operations costly, non-transparent, error-prone, inefficient and environmentally non-sustainable.

Figure 5: Motivation & Cross-Domain Requirements

3.1.1 Business Impact

As depicted above, modern international business – especially in the large and global industries of Agri-Food, Transport and Logistics – is a highly competitive endeavour where resource constraints require organizations to partner with one another to efficiently and effectively address customer needs. In this dynamic market new challenges continually arise, particularly due to increasing customer expectations for personalization and cost reduction. As analysed in detail in the preceding FI PPP Phase 1 use case pro-jects (SmartAgriFood

1 and FInest

2), current ICT technologies are either too limited or not capable of

properly supporting this evolution of customer requirements. To overcome this and pioneering towards possible future business collaboration platforms, the FIspace will facilitate the following business benefits:

1 see project website: http://www.smartagrifood.eu/

2 see project website: http://www.finest-ppp.eu/

http://www.smartagrifood.eu/

http://www.finest-ppp.eu/

FIspace 11.11.2015


Better satisfy customer requirements, such as:

End-to-end visibility and event management,

Enhanced monitoring and tracking of goods as they move along the value chain,

Less costly and better tailored offers goods and services,

Significantly reduced waste of perishable products,

Immediate notification of deviations and the occurrence of hazardous events,

Lower environmental impacts through increased network efficiencies, and

More transparent operations.

Substantially increase business efficiency and optimization throughout the entire value chain by:

Significantly reducing manual efforts for planning and replanning,

Enhancing interoperability among heterogeneous systems based on business standards,

Automating support for coordination of operational activity execution,

Providing accessibility anywhere and anytime via any device, and

Facilitating the rapid identification and contracting of capable business partners.

Facilitate new business opportunities by:

Providing more efficient and transparent service offer management,

Optimizing partner contract negotiations,

Facilitating new business partner interactions and collaboration opportunities, and

Providing access to true end-to-end business and consumer performance metrics.

On a broader perspective and with respect to the program-level objectives of the FI PPP, the idea behind the FIspace is to truly move forward in conceiving of a new paradigm in computing that is based on emerging Future Internet technologies and leverages the full potential of the cloud-based services con-cept. The FIspace pushes boundaries on how business software will work in the future, facilitating innova-tion and market impact by laying the foundation for adoption by large user groups and external solution providers that can provide additional, novel, and disruptive Apps for the FIspace. In the context of the FI PPP, the FIspace complements the mission of the FI PPP Core Platform Objective: while “FIWARE aims to provide a framework for development of smart applications in the Future Internet”, the FIspace will exploit its technologies for enabling substantial increases in the efficiency and effectiveness of cross-organizational business processes and pioneer novel business models that allow for innovation by exter-nal stakeholders with high prospects for industrial uptake and market impact. An important point to note is that the innovative aspect of the FIspace model is the model itself (covering both the technical solution and the proposed business model) – it is not any specific ‘technology innovation’ such as, e.g., new algo-rithms, software engineering concepts or the like (see also chapter 7 on innovations).

3.1.2 Main Features and Building Blocks

As outlined above, the FIspace is a Future Internet enabled cloud-based SaaS-platform for enabling the seamless, efficient, and effective business collaboration across organizational boundaries and facilitating the establishment of ecosystems with business benefits for both users from industrial sectors as well as the ICT industry. The FIspace was realized on the basis of FIWARE technologies that are developed in the FI PPP, and utilized several Generic Enablers (GE). In addition, desirable domain-specific capabilities were developed to demonstrate the value and capabilities of the FIspace technology and business model (i.e., for inter-organizational process coordination, operational monitoring and tracking, event-driven re-planning, ecosystem application development, monetization, security and privacy management in busi-ness networks, etc.).

FIspace 11.11.2015


Figure 6: Main aspects of the FIspace platform components in relation to the high-level conceptual architecture.

In order to realize the envisioned features – i.e., (a) the future support for collaboration in business net-works, and (b) a future business model for rapid development of high-quality ICT solutions at minimal costs – the FIspace consists of the following primary building blocks as shown in Figure 6:

The Front-End that serves as the main point of access for End-Users and offers a novel ‘all you need in 1 place’ user experience, including the following main features:

Customizable End-User Cockpits

Social Networking and Collaboration Features for Business Partners and Communities, and sup-port for seamless collaboration on specific business activities and transactions

Access anywhere via any device.

The FIspace Store that provides the tool-supported infrastructure for providing, finding, and purchas-ing FIspace Apps that provide re-usable IT-solutions for seamless business collaboration and can be used and combined for the individual needs of End-Users; for the, the FIspace Store includes:

The software infrastructure to support the provisioning, consumptions, purchase, and re-use of FIspace Apps for both End-Users and App Developers

Financial Management of the FIspace (pricing, payment, revenue sharing).

The Business Collaboration Core Modules ensuring that all information and status updates are provid-ed to each involved stakeholder in real-time, consisting of:

A Collaboration Engine that captures, in form of so-called Business Entities, the information that are to be exchanged among collaborating stakeholders along with status and control of the a col-laborative business processes, and

An Event Manager that captures and pre-processes both manual (from humans) and automated (from connected systems) events, which trigger the progress and activities of collaborative busi-ness processes in a pro-active event-driven manner.

A System and Data Integration Layer that allows for the integration and continued usage of existing legacy and business systems as well as the integration of external systems and services, including sup-port for:

Connecting business and legacy systems used by individual users

Handling heterogeneous data

Connecting external Systems and Services (e.g., IoT systems, 3rd

party and public services).

FIspace 11.11.2015


A comprehensive Security, Privacy, and Trust framework that ensures the secure, reliable, and trust-worthy handling of business data making the FIspace ‘secure by design’, including esp.:

Access Control and Identity Management for all users

A set of Security Mechanisms to ensure information security, attack prevention, etc.

Developer support to ensure correct usage of necessary security mechanisms in FIspace.

An Operating Environment that ensures the technical interoperability of FIspace Components and Apps and the consistent behaviour of the FIspace, including:

Technical Interfaces and Protocols for the FIspace Components and Apps

An Enterprise Service Bus to support the interaction of FIspace Components and Apps

Replication and Consistency Services to ensure fault-tolerance and transaction support.

A Development Toolkit providing tool-support for the development and instantiation of FIspace, particu-larly for:

App Developers to support the development and provisioning of Apps in accordance to the tech-nical governance and procedures of the FIspace

Business IT Experts who customize and extend the FIspace to the individual needs of End-Users at an individual or organizational level.

Therefore, the main features of the FIspace can be summarised as follows:

An open application that can be extended and customized for specific stakeholder requirements through the use of Apps that can be “mashed up” (integrated) using services of the FIspace (an ex-tension of the app concepts of mobile telephone providers such as Apple, Google and Microsoft);

An integrated Front-End as a central point of access to all features and Apps, enabling an “all you need in 1 place” user experience with customizable views for individual users;

Integrated novel technologies that provide the basis for future collaboration in business networks, enabling “all information to each stakeholder in real-time” as well as the seamless interaction and co-ordination among business partners;

Information integration from legacy and third party systems enabled through a service-based integra-

tion layer that is enabled and supported by FI-WARE Generic Enablers;

Modern technologies that ensure the secure, reliable, and trustworthy handling of business infor-mation in the Cloud, and the consistent operation of the FIspace;

An (App) Store that facilitates the provisioning, consumption, and marketing of novel on-demand solu-tions for B2B collaboration, along with an integrated toolkit for developers.

FIspace 11.11.2015


3.2 FIspace Operation Model – Illustrative Example

While the overview above remains on a general level, the following explains the operational model of the FIspace at hand of an illustrative example. For this, we use the ‘Spraying Advice’ scenario as the sample use case: taken from the Greenhouse Management & Control trial (see also section 3.4.2), this has been taken up for the scenario-based technical design of the FIspace components and their consolidation. It is important to note that the scenario and FIspace Apps as described below are a simplification only intend-ed for illustration; the actual scenario analysis and FIspace-based solutions for this were elaborated in further detailed are documented in the related project reports.

3.2.1 Sample Scenario: Spraying Advice

The sample scenario considers a situation where a farmer (here: Franz Farmer) demands a spraying advice from an expert (here: Ed Expert) in order to handle a disease on tomatoes in his greenhouse; as an additional stakeholder, a local state authority is involved who needs to approve the usage of the pesti-cide recommended by Ed because of its environmental impacts. As indicated above: this scenario and the stakeholders are fictitious and only intended for illustration purposes.

Figure 7: Sample Scenario 'Spraying Advice' - AS IS Overview

Figure 7 above provides an overview, indicating the current situation (AS-IS): Franz calls up Ed and ex-plains the situation. To be able to provide adequate advice, Ed needs more detailed information on the tomatoes and the current situation; for this, commonly Ed needs to visit Franz’s farm onsite in order to investigate the disease and get the relevant data from Franz’s farm management system (product details) and the sensor network in the greenhouse. After Ed Expert has concluded the advice (using, among other sources, his own expert system), he files the request for the necessary state approval by letter; the au-thority approval is finally given again by postal letter to Ed and Franz.

This creates a lot of overhead, creates costs, and delays the time until Franz can undertake the neces-sary actions to handle the disease. The purpose of FIspace is to overcome this by enabling to conduct all necessary interactions ‘online’ where the involved players conduct the business interaction via Apps that are connected to the relevant on-premise systems and inform each stakeholder about the current status of the collaboration business process in real time. Figure 8 below outlines how the TO-BE scenario shall look like: all involved stakeholders perform the information exchange and communication between them via the FIspace, using dedicated FIspace Apps that, for instance, allow Franz to send his request for ad-vice directly to Ed via the FIspace and provides Ed with remote access to the greenhouse sensor data, and also the spraying approval by the state authority is requested and processed ‘online’ via the FIspace. In addition, the stakeholders’ respective back-end systems are connected to the FIspace, so that the in-formation will needs to be exchanged among the stakeholders can be imported into the FIspace Apps, which allows decreasing manual effort and quickly setting up individualized solutions for collaboration

FIspace 11.11.2015


business activities with full control on the information sharing by each participating business partner. With this, the FIspace enables the seamless, efficient, and easy business collaboration and eventually will facilitate the business benefits as outlined above.

Figure 8: Sample Scenario 'Spraying Advice' - TO BE Overview

3.2.2 Illustration of FIspace Apps and Overall Operational Model

To illustrate how the TO BE Scenario shall actually be realized with the FIspace, let us first investigate a typical FIspace App. For this, Figure 9 shows an illustrative design of the ‘Get Spraying Advice’ App that is used by Franz Farmer. It consists of three main functionalities: on the left hand side, Franz can prepare the Request for Advice (incl. basic product information, a description of the request, and a link to the IoT-enabled sensor network in his greenhouse), and select the receiver of the request from the business con-tacts that Franz maintains in the FIspace. Once the advice is prepared, Franz can receive it and optional-ly conduct additional interactions with the business partners (see right hand side for some initial ideas). An important and novel feature of the FIspace is that Franz can always see the actual status of his re-quest (see bottom): this is automatically updated whenever a partner undertakes an action (e.g. when Ed Expert has finished the preparation of the advice, or when the state authority has provided the approval).

Figure 9: FIspace App ‘Get Spraying Advice‘ – Illustrative Design

FIspace 11.11.2015


With this kind of FIspace Apps, each involved stakeholder can see all relevant information in one place and is informed on status updates in real-time, especially on critical situations such as delays or other deviations that often are business-critical and hence are demanded to be known as quick as possible. In addition, such FIspace Apps can be developed rather quickly, which allows businesses and partner net-works to promptly adapt their collaborative IT-infrastructure with respect to newly arising market opportu-nities.

Figure 10: Illustration of FIspace Overall Operational Model

Figure 10 provides a visualization for explaining how the FIspace is intended to work. When the stake-holders log on to the FIspace, they can see their new notifications (similar to ‘new messages’ in e.g. face-book) and access their respective FIspace Apps: e.g. Franz the one outlined above, Ed Expert an analo-gous one that supports the creation of advices and seamless interaction with his business partners, and another one for the State Authority to handle spraying approvals. The execution of the cross-organizational interaction is facilitated by the generic FIspace platform-features, in particular by:

(A) The Business Entities that represent the collaborative business process and control its execution by managing the interaction and control flow between the associated apps, for example:

When Franz sends out a ‘Request for Advice’ via the FIspace App from Figure 9, the underlying Business Entity triggers a process step which ensures that Ed Expert is immediately notified about a new request within his personal FIspace Front-End, resp. FIspace App;

When the State Authority provides the spraying approval, both Franz and Ed are notified immedi-ately within their respective Front-End / Apps.

(B) The Event Engine that captures and processes various types of events that are used to e.g. trigger the progression of Business Entities or alert End-Users on critical situations, therewith making the FIspace an event-driven platform; examples for events are e.g.:

A new ‘Request For Advice’ send out by Franz or another Farmer is an event, which triggers the progress of the Business Entity as described above, or

Franz can get notified on external events that maybe critical for his business (e.g. temperature in the Greenhouse reaches a threshold, or an upcoming thunderstorm),

(C) The Access Control which ensures that only those people get access to information who have the respective permissions and nobody else (ensured by the all-embracing Security-Privacy-Trust framework of the FIspace), and also the reception of notifications in accordance to the personal configurations and settings of the user’s profile in FIspace.

FIspace 11.11.2015


(D) The ‘System & Data Integration’ facilities that allow to quickly set-up connectors or adapters to exist-ing system landscapes using standard technologies and data formats so that Franz, Ed, and the State Authority to connect their respective back-end systems to the FIspace, e.g.:

Franz can grant Ed access to the IoT-enabled sensor network in his greenhouse via the FIspace (similar to e.g. sharing a link or video with friends in facebook), or

The State Authority can upload details on the spraying approval from its existing in-house regula-tions and approval management system landscape.

Of course, also the other technical building blocks as identified above in Section 3.1.2 are important and needed in order to ensure a proper execution and usage of the FIspace: The Operating Environment ensures the technically smooth interoperation of all components and also the fault-tolerant execution, which is of high importance when dealing with business-relevant data and processes; the Development Environment provides the tool support for the developers of FIspace Apps and ensures that the imple-mentations comply with the FIspace standards for security and technology, and as the marketplace for FIspace Apps the FIspace Store provides the basis for the economic exploitation of the FIspace.

FIspace 11.11.2015


3.3 The FIspace Platform Main Components

The previous sections were introducing the main features of FIspace. This section is further detailing the individual components to facilitate an understanding of the finally implemented results.

3.3.1 FIspace Front End Component

The User Front-End builds the main access point for users of the FIspace platform. Through the integra-tion of external widgets (e.g., from the store, externally developed Apps or other external providers), the User Front-End facilitates an ‘all you need in one place’ user experience and creates a central access point. To support the diversity of FIspace users and devices the User Front-End will be adaptable to spe-cific needs, tasks and roles. Beyond the adaptation to different devices, the User Front-End also supports some customization of the user interface. The Front-End also enables users to create relations to busi-ness partners to facilitate the communication among them (comparable to modern social networks).

User Front-End has been developed as a web application. This web application can be accessed from several devices using its specific URL. All the information related with the User Front-End is stored in a relational database located in the same machine and environment.

In order to let other applications to access to FIspace Front-End database, a Rest API is provided. This API is being used by another User Front-End approach that has been developed as proof of concept, a Java FX application. This application can be executed as desktop application offering FIspace users an-other user experience.

Figure 11 shows an overview of User Front-End component.

Figure 11: Overview of User Front-End component

The current version of FIspace Front-End provides to the final user the following functionalities.

User Profile: Users can create a Personal Profile. In this profile different personal information can be shown and edited. Also profile picture and cover picture can be uploaded. If you visit an-other user profile you can add his/her profile as Friend.

Company Profile: Users can create a Company Profile. In this profile different company infor-mation can be shown and edited. Also profile picture and cover picture can be uploaded. If you visit a company profile you can follow this company. Who creates the Company Profile is auto-matically its administrator.

Search: User and Company profiles can be found using search bar. It searches in all the users and companies names the string that you wrote in search field.

FIspace 11.11.2015


News: Home Page where users can post news or information to other FIspace users. Users can post this information as user or as Company (If user is company profile administrator). Each user only sees his friend’s news and posts from companies he is following. In each post Ed-it/Like/Comment/Share actions can be performed.

Guided tour: In welcome page a Tour option that explains each menu option to new users can be started.

Chat: Users can communicate with other FIspace users using chat functionality. Conversations are store in user browser in order to continue a conversation later if browser is closed.

Friends/companies suggestions: In the welcome page Users obtain Friends/Companies sug-gestions.

These suggestions are generated with the following criteria:

o Friends Suggestion:

If User doesn't have any friend yet he/she gets users from the companies he/she follows.

If User has friends he/she gets friends of his/her friends (1st level relationship on-ly).

o Companies Suggestion: Most popular ones. All companies ordered by number of fol-lowers in descending order.

Help: All options in FIspace Front End are described in this section in order to help new users to understand the different functionalities.

Theme Customization: Users can select 2 different themes for FIspace Front End (Default Theme or Amelia Theme) to give them the possibility to customize some visual aspects as col-ours or fonts.

Private Profile: Users can make their profile private. In case he/she actives this option, his/her profile is not going to appear in search results.

Email new News: Users can receive in their email what their friends post in FIspace. An auto-matic mail is sent containing the new post.

User Analytics: Users can see how many users has visited their profile and who of these visits are already friends or not. Also there is a measurement of profile completed.

Internal Messages: Users can send internal messages to other users. Usual messaging actions are provided (Reply/Forward/Resend/Save as Draft/Mark as Favourite).

Different Languages available: Users can select different languages for FIspace Front-end op-tions and Menus.

Advanced Search: Users can search other users or companies using different filters.

More themes: FIspace Frontend offers more than Default or Amelia theme. A complete list of themes will be available. Also users can download a .css template and modify it in order to cus-tomize completely FIspace Frontend.

Kanban Board: Users have a personal Kanban Board in order to manage there all his/her per-sonal task.

Business & Capabilities: Depending on the FIspace user role (Business Architect, App Devel-oper or user) he/she has access to a new section where new Business process or capabilities can defined to be used by new apps.

Responsive adaptation: FIspace can be visualized correctly in different devices.

3.3.2 FIspace Store Component

The FIspace Store is tool-supported infrastructures for the provisioning, consumptions, purchase, and re-use of IT-solutions for seamless business collaboration. The FIspace Store supports the Financial Man-agement of Apps (pricing, payment, revenue sharing) for both End-Users and App Developers.

The FIspace Store provides the core elements for the monetization of Apps throughout the FIspace eco-system. App Developers publish and manage the financial aspects of Apps, while End-Users search and consume Apps.

FIspace 11.11.2015


App Developers are provided with an Apps Interface discovery system, publication support tools and fi-nancial management tools. The Apps Interface discovery system is used to reuse functionality and build mashup applications. The publication support tool provides an integrated compliance check that eases the publishing of new Apps. The financial management tools enable developers to run statistics, define revenue models and share revenue with any involved partner (e.g. developer of re-used component).

End-Users are provided with a search, purchase and execution support system. The search system al-lows End-Users to find applications according to a set of parameters. The purchase support system guides End-Users in the purchase process for Apps. The execution support system provides End-Users with download and installation guides, in case of locally run Apps, and access control systems for Apps executing in the Cloud. A simple right management system enables End-Users to customize Apps after purchasing.

All Apps are stored in an App repository. As shown in the Figure 12, the FIspace Store has 2 main user groups: Consumers as the (Business) End-Users who utilize the FIspace apps to conduct business tasks (esp. the collaborative business activities across organizational boundaries), and App Developers who develop Apps for the FIspace.

Figure 12: FIspace Store Overview

A Consumption Support component provides the necessary software infrastructure to find and re-use Apps. A Purchase component supports the purchasing process including buying an App (e.g. terms and condition agreement) and paying for it. A Provisioning Support component enables developers to easily upload and publish newly developed Apps, including technical compliance checks. In addition, the Finan-cial & Revenue Sharing Manager, who is part of the FIspace App Repository, handles the monetary in-comes and the revenue sharing.

Technically, the FIspace Store and the necessary software infrastructure are developed on top of existing frameworks and technologies. Primary candidates are the Generic Enablers from the FI-WARE IoS Chap-ter, using (Linked) USDL as the basis for the App Description Language, the Service Repository as basis for the FIspace App repository and the Marketplace GE as basis for features of the Consumption Support and Provisioning components.

Figure 13 shows the high level composite architecture for the Store components.

FIspace 11.11.2015


Figure 13: Store – High level composite architecture

The High level composite architecture related to the store components is composed by the mains building block:

SDK: Provide the functionality to upload apps to the Store component using the SDI´s interface.

SDI: The entry point to FIspace, allows the communication between the components that inte-grate the platform.

Front-End: The gateway to FIspace for users of the platform. Through the integration of external widgets (e.g., from the store, externally developed Apps or other external providers), the User Front-End facilitates an ‘all you need in one place’ user experience and creates a central access point.

The GEs required by the store components are the followings:

WStore: Keeps track of Offerings and Resources in FIspace. Offerings are represented by an of-fering description and offering image, and are composed of a set of resources.

Wirecloud: Integrates heterogeneous data, application logic, and UI components (widg-ets/gadgets) sourced from the Web to create new coherent and value-adding composite applica-tions.

Repository: Provides a consistent and uniform API to Linked USDL service descriptions and as-sociated media files

Marketplace: Provides functionality necessary for bringing together offering and demand for mak-ing business. These functions include basic services for registering business entities, publishing and retrieving offerings and demands, search and discover offerings according to specific con-sumer requirements as well as lateral functions like review, rating and recommendation.

FIspace 11.11.2015


The architecture of the Store is divided in two clearly separated domains: the FIspace platform and the FIWARE Business Framework GEs.

The FIspace platform includes all the FIspace internal components. In the picture we have only included those that interact with the Store. FIspace is a tightly integrated system with a SSO facility, provided by the Keycloak IDM, and an internal communication system, provided by CSB.

The FIWARE Business Framework GEs is an ecosystem of Generic Enablers provided by the FIWARE foundation for implementing different business processes. The ones relevant for the FIspace Store are the ones implementing the App publishing and purchase capabilities. These GEs are WStore, Wirecloud, Repository and Marketplace. These GEs are integrated with each other, but exists outside the FIspace platform. That means that they do not communicate using CSB and, generally, don´t integrate with the SSO system. As an exception, WStore and Wirecloud GEs have been modified to support the FIspace SSO system, since these GEs are in direct communication with FIspace components.

The Store component exposes its API to the FIspace platform through CSB. This API is consumed by SDI, which exposes all FIspace APIs to software external to the platform. The main consumer of the Store API is the SDK, which uses its functionality to create Apps in the system.

Store component publishes user Apps in WStore, which in turn publish Apps in the Marketplace and makes them visible in Wirecloud. Then, the Front-End uses Wirecloud to allow users to purchase, use and mashup Apps. This flow of information implies that there is communication between Store and Front-End, although this communication is indirect between GEs interaction, and not directly between compo-nents.

In summary, the following features are provided:

App deployment and management.

App purchase.

Revenue Sharing model for Apps.

3.3.3 Business to business (B2B) component

At the heart of the envisaged FIspace platform reside the Business-to-Business (B2B) Core Modules. The B2B Core ensures that all information and status updates are provided to each involved stakeholder in real-time. The B2B core allows for the creation, management, execution, and monitoring of collaborative business processes in the FIspace platform. The B2B Core consists of two interrelated and complemen-tary components:

A Collaboration Engine that captures, in the form of Business Entities, the information to be ex-changed among collaborating stakeholders along with status and control of the a collaborative business processes. The BCM component is responsible to orchestrate the different processes from different stakeholders and assure the correct sequence of the tasks execution.

An Event Processing Engine that detects and analyses events coming from activities in the col-laborative processes or from IoT devices. The Event Processing Module (EPM) component moni-tors events and detect situations of interest in real-time, i.e., situations that require appropriate re-actions.

The BCM component is responsible to orchestrate the different processes from different stakeholders and assure the correct sequence of the tasks execution. The BCM is based on the entity-centric approach (for more details, please refer to the outcomes of the ACSI project - Artifact-Centric Service Interoperation (ACSI)).

This approach relies on the notion of business entities (aka, as (dynamic/business) artefacts). These pro-vide a holistic marriage of data and process, both treated as first-class citizens, as the basic building block for modelling, specifying, and implementing services and business processes.

A (business) entity is a key conceptual concept that evolves as it moves through a business (or other) process. An entity type includes both a data schema and a lifecycle schema which are tightly linked. The data schema provides an end-to-end conceptual view of the key data for this entity type. The lifecycle schema of an entity type specifies the different ways that an entity instance might evolve as it moves through the overall process. In FIspace we apply the GSM (Guards, Stages, and Milestones) model to specify the lifecycle schema of the business entities.

http://www.acsi-project.eu/

FIspace 11.11.2015


BCM tooling: The BCM relies on and extends the BizArtifact open source tool, a.k.a ACSI, (both design and run times)

The Event Processing Module (EPM) component monitors events and detect situations of interest, i.e. situations that require appropriate reactions. The events sources (aka events producers) can be the actu-al execution of the collaboration (i.e., the BCM), external systems, or sensors.

The EPM processes these events and by applying pattern matching derives situations of interest. Exam-ples of situations of interest can be: Missing documentation at a certain point in time, a sensor reading outside a permitted range, or a delay in a delivery. In general, we can distinct between situations that result from the actual execution of the process or collaboration and situations that result from external events (i.e., events coming from external systems or sensors).

These two modules are connected each to the other and to the other FIspace components of the platform via the Cloud Service Bus (CSB) component (See section of the corresponding document related to the CSB and online documentation in http://dev.fispace.eu/doc/wiki/csb).

EPM tooling: The EPM relies on and extends the CEP GE (Complex Event Processing Generic Enabler), a.k.a Proton, from FI-WARE (both design and run times)

3.3.3.1 Main features

We outline below the main features that have been extended to both the BCM and EPM engines. To bet-ter understand the modus operandi in each engine, please refer to the “B2B Core Modules documenta-tion for business architects” document.

BCM

BizArtifact tool comprises a run-time engine and a design-time authoring tool using a single declarative programming model (GSM).

The BCM extends the BizArtifact open source tool as follows:

Templates support

Integration with the CSB

Request/response (sync. mechanism) support

Query API support

EPM

Proton comprises a run-time engine, producers, and consumers with the characteristics and capabilities to develop, deploy, run, and maintain event driven applications using a single declarative programming model.

The EPM extended the CEP GE from FI-WARE as follows:

New operators: TREND (increasing and decreasing functions)

Templates support

New adapters for the CSB

Figure 14 shows the high level composite architecture for EPM.

http://dev.fispace.eu/doc/wiki/csb

FIspace 11.11.2015


Figure 14: High level composite architecture for EPM

Figure 15 shows the high level composite architecture for BCM.

Figure 15: High level composite architecture for BCM

FIspace 11.11.2015


3.3.4 System and Data Integration (SDI) Component

The component called System and Data Integration (SDI) is a part of the core platform of the FIspace Project, and it can be defined as the gateway or entry point of the platform. In other words, this module is in charge of the communication between the “outside” world and FIspace. This communication is done in a bidirectional manner.

To communicate with external systems, the SDI offers a RESTful API. Also, whenever the SDI has to send information to an external system, the SDI expects the external system to provide a REST API ac-cording to FIspace SDI’s approach/guidelines, i.e the so-called “capabilities model” (see below). The next figure shows an overall picture of the SDI and its interactions with other modules. While the communica-tion with the “outside world” is done via REST, the communication with other FIspace components is done via the Cloud Service Bus (CSB).

Figure 16: SDI interaction model overview

It should be noted that the so called “FIspace apps” are, from a technical point of view, seen as external systems and therefore have to use the SDI as gateway in case they want to send messages to other FIspace components (e.g. business collaboration messages to the B2B module or notification messages to the GUI). Therefore, in the following text the term “external system” also includes “FIspace apps”.

As an integration tool, the SDI uses Apache Camel3 technology, which is a versatile open-source integra-

tion framework supporting known Enterprise Integration Patterns.

In order to develop as much as possible a scalable and generic component, recently a new concept has been introduced to expose the communication interface through the so-called “capabilities model”. This new approach is meant to facilitate the business to business collaboration, by offering capabilities that can be used in a business process (an example could be the capability “provide greenhouse advice”, which is provided by a greenhouse expert and can be used in a “greenhouse advice business process” by a farmer who is searching for advice). In other words, capabilities are services that FIspace or a connect-ed external system offers. From a technical point of view, each capability defines how a specific message exchange between FIspace and an external system works (e.g. which request message is sent, what is the expected response, REST method used, URL of the external system that provides the capability). As some typical capabilities like “provide product information” or “provide shipment information” could be used in several business processes and could be provided by different types of systems, there is also a generalization of capabilities foreseen: the so-called “capability types” define capabilities in a reusable

3 Camel provides the tools to define routing and mediation rules in a variety of domain-specific lan-

guages, including a Java-based Fluent API, Spring or Blueprint XML Configuration files, and a Scala DSL. Camel provides the tools to define routing and mediation rules in a variety of domain-specific languages, including a Java-based Fluent API, Spring or Blueprint XML Configuration files, and a Sca-la DSL. Apache Camel uses URIs to work directly with any kind of Transport or messaging model such as HTTP, ActiveMQ, JMS, JBI, SCA, MINA or CXF, as well as pluggable Components and Data For-mat options permitting to work with the same API regardless which kind of Transport is used. (http://camel.apache.org/)

http://camel.apache.org/

FIspace 11.11.2015


way, so that different systems that implement a specific capability type can be used (replacing each oth-er) in the same process.

The general high-level architecture of the SDI is depicted in the figure below.

Figure 17: SDI high-level architecture.

As it can be seen in the figure, there several modules that compose the SDI are:

WEB: This module is implemented using Apache Camel technology, and it is the resulting application of the junction of the different SDI components. It enables the communication between the external systems or apps and the different modules of the SDI providing a complete set of functionalities. The different required modules that compose the WEB module are included using maven technology, in other words, included as maven dependencies.

Core: SDI provides an implementation of the FIspace Core API. The FIspace Core is directly related with the different domains, as it the responsible for the management and maintenance of the different messages or interfaces that the FIspace platform is going to expose. This module can be considered as the “core” of the FIspace platform.

Domains Specific Messages and Interfaces: FIspace offers its platform for different domains of application. Depending on the requirements of each “FIspace app”, each domain module will be the responsible for its correct management among the platform.

CSB Wrapper: Java code in charge of the exchange of information between the SDI and the CSB.

Registry: This component represents the database used by the SDI. Depending on the requirements of the user it can be configured to use an Apache Derby database or a MySQL database.

3.3.5 Operating Environment Component

The Cloud Service Bus (CSB) layer of FIspace Operating Environment is the middle-ware that enables integration of different FIspace service components and applications. CSB provides a set of integration interfaces and qualities of service, required to support a wide spectrum of information exchange scenari-os, ranging from best effort notifications, to guaranteed delivery of transactional data.

The Cloud Service Bus has virtually unlimited scalability, both in the number of supported end-points, and in the number of communication channels allowed by the Bus transport fabric.

The CSB provides the following main services and corresponding API:

Publish/subscribe

Queuing

Synchronous Request/Response

FIspace 11.11.2015


Asynchronous Request/Response

Time-limited asynchronous Request/Response

Network time service

The description of the API operation is detailed in the next subsections.

3.3.5.1 Publish/subscribe

Topic-based publish/subscribe is an efficient tool for scalable message distribution to multiple clients. A topic is a virtual address, where any client can send (‘publish’) a message, and any client can listen (‘sub-scribe’) to the published messages. Publish/subscribe is optimal for fast and scalable distribution of real-time data. However, it provides either best effort or partially reliable qualities of service. The mode of data delivery is synchronous - receivers need to be online when a message is published, and have to keep up with the transmission rate.

3.3.5.2 Queuing

Unlike Topics, Queues are physical objects, with an associated persistent storage on a hard disk. Any client can send a message to a queue, where it will be written to a disk and replicated for high availability. Any client can consume the queued messages. Queuing is the most reliable and consistent data delivery method, supporting persistence, identical message ordering and high availability qualities of service. Also, queues allow for fully asynchronous data exchange – much like in email, receivers don’t have to be online when messages are sent; they can join a queue any time later and retrieve the stored messages. In terms of throughput, one queue can support around a thousand messages per second (just a rough estimate). Topics are a few times faster, but less reliable.

When using messaging, choose either pub/sub or queuing for each channel of communication, according to your application quality of service requirements.

3.3.5.3 Synchronous Request/Response

This mechanism allows clients synchronously query one another for a value of specific attributes or for any other information. Both query (request) and response are POJO objects, in a format that is mutually agreed upon between requesting and responding applications or components. This flexibility allows any kind of input data to be provided in the request, and any kind of output data delivered back as a response. The requester sends a request and waits for a response, up to a specified timeout. The responder re-ceives the request, produces a response and sends it back as soon as possible.

Synchronous request/response is optimal for applications where the response information can be re-trieved quickly by the responder, so the requester won’t have to wait a long time on a blocking query.

3.3.5.4 Asynchronous Request/Response

Sometimes, a response cannot be produced immediately – it might involve heavy on-spot data pro-cessing, or an interaction with a third party, or other factors with unpredictable timing. Moreover, some applications might need multiple responses to a single request – for example, future notifications upon attribute value change. Asynchronous request/response mechanism supports this functionality, by allow-ing requester to set a response listener callback, and by enabling the responder to send response mes-sages at any time, without a limit of number of responses for each request.

3.3.5.5 Time-limited asynchronous Request/Response

This mode addresses the following scenario – the time required to produce a response is more or less known (predictable), but is long, so the requester is not willing to be blocked on a synchronous request. In this case, the requester should send an asynchronous query, and set a CSB response timer. If no re-sponse to this specific request arrives with the specified time, the requester will be called with WAIT_TIMEOUT notification.

FIspace 11.11.2015


3.3.5.6 Network time service

CSB provides a simple implementation of the NTP protocol, which finds the time difference between clocks of different machines. This service allows all machines, running CSB, to use unified time stamping that refers to the same clock (that of the coordinator machine).

3.3.5.7 High level composite architecture

The scalability challenge, posed by the large number of data producers, service providers and consumers in this cloud-based project, is addressed by Peer-to-Peer overlay technology. The CSB core is comprised of Bus Nodes, connected by a peer2peer structured overlay fabric. The CSB clients are the FIspace ser-vice components and applications, using the Bus for integration and connectivity. This two-tier architec-ture allows us to build an enterprise-strength service bus, with extensive functionality set and assured delivery of transactional data. The CBS supports multi-tenancy, enabling creation of separate Bus do-mains, each using a different P2P overlay structure.

Figure 18 shows the CSB architecture. The blue boxes are the CSB Nodes, connected by a peer-to-peer overlay ring (red dash line). Green blobs are the CSB clients – applications, services or mediations, using CSB for connectivity.

Figure 18: CSB high level architecture

3.3.6 Security, Privacy and Trust Component

The aim of the Security, Privacy & Trust (SPT) framework of the FIspace platform is to provide secure and reliable access and, where needed, exchange of confidential business information and transactions using secure authentication and authorisation methods that meet required levels of security assurance. Authentication, authorisation and accounting technologies will provide user management & access control features.

Initially; Digital Self GE and Access Control GE were planned to be used for authentication and authorisa-tion. Authentication, user management and authorisation functionalities were tested successfully using these GEs. However when security related GEs became obsolete then security team initiated the mitiga-tion plan to provide the Security, Privacy and Trust component.

Mitigation plan consist of open-source solution Keycloak (http://keycloak.jboss.org/). It basically provides Integrated Single Sign-On (SSO) and Identity Management (IDM) for browser apps and RESTful web services. Built on top of the OAuth 2.0, Open ID Connect, JSON Web Token (JWT) and SAML 2.0 speci-fications. Options are to deploy it with an existing app server, as a black-box appliance, or as an Openshift cloud service and/or cartridge.

Role Based Access Control functionalities are provided under the “realm” - concept of a Keycloak. A realm secures and manages security metadata for a set of users, applications, and registered OAuth clients. Users can be created within a specific realm within the Administration console. Roles (permission types) can be defined at the realm level and you can also set up user role mappings to assign these per-missions to specific users.

http://keycloak.jboss.org/

FIspace 11.11.2015


SPT package is being used by FIspace Front-End, and Single Sign-On functionality provides seamless access between the Front-End, WireCloud and WStore components. User management is being done federatively by SPT package.

In WP300, the task T350 “Experimentation Environment’s web application” was fully integrated with this new SPT package for the user authentication. Associated roles defined for the environment and UI is customized based on the role of the authenticated user.

Integration of this new SPT package to Logistics Planning Application is also successfully completed. Concerning the RBAC system, security policies have been defined based on the use case scenarios and these roles are currently used for in Logistics Planning Application (LPA).

SPT package currently provides major security functionalities including; user authentication, SSO and Single Log Out for browser applications, user registration, forgot password support (user can have an email sent to them to reset password), user session management. Admin can view user sessions and what applications/clients have an access token. Sessions can be invalidated per realm or per user.

3.3.6.1 High level composite architecture

Keycloak provides Single Sign-on functionalities along with the APIs required for the management. Both FIspace platform and external applications running on FIspace platform use the SSO layer to provide secure authentication and retrieve user information. However management APIs are only to be used by the FIspace platform, more specifically FIspace Front-End.

Figure 19: SPT high-level architecture

3.3.7 Software Development Kit

FIspace Software Development Kit (SDK) is a collection of plugins developed for the Eclipse platform that together make an IDE for the development of applications in FIspace. In this environment it's possible to edit different code, scripts with syntax highlight, code completion, compilation errors, code and comment folding, script execution with a pre-configured interpreter, besides the tools that the eclipse platform pro-vides.

The main goal of the project is that new tools will be developed using the extension architecture that the Eclipse platform provides and that FIspace SDK has available for extension of its capabilities.

Besides the seventeen FIspace plugins already implemented, the FIspaceStudio Tool is also updated. The binary distribution of FIspace SDK is represented by an Eclipse Rich Client Application. The distribu-tion provides the required user interface for all of the pre-installed FIspace SDK functionalities along with a customised approach of the Eclipse IDE reaching the specific needs of FIspace platform. A set of li-

https://www.eclipse.org/

FIspace 11.11.2015


braries implemented in several programming languages is being developed, in order to provide the FIspace user with the appropriate tool to connect to the platform.

Main features delivered:

Project templates: a new RCP archetype has been implemented and some enhancements have been done in order to connect to FIspace platform (decoupled archetype provides authenticated connection).

Preferences window: archetypes settings have been widely enhanced.

Uploader plugin: new plugin for storing apps (not backend parts) in FIspace. Security feature is being added.

Access to authoring tools (BCM editor and EPM editor):security issues are being faced.

Graphics view plugin: this plugin is now working. The REST plugin was enhanced, and also the Publisher/Consumer one. The Converters (Transformers) plugin is working with the available for-mats, and the Widget artifact is ready for apps being uploaded.

Import plugin: new plugin implemented for importing FIspace projects (widget and decoupled ones).

Export plugin: new plugin implemented for exporting FIspace projects.

Logging plugin: this plugin has been extended to provide a back-end to store all generated logs in a database (back-end is developed in Nodejs and database in MongoDB).

FIspaceStudio Tool: some improvements have been implemented in order to make it more use-ful to the final user (now, you can install more software). Some old bugs have been also fixed.

Libraries to access FIspace platform: several libraries are being implemented in different pro-gramming languages (C#, JavaScript and Python libraries are in progress. PHP library is also planned). The aim of these libraries is to provide the corresponding access to FIspace services based on OAuth2 protocol.

FIspace 11.11.2015


3.3.8 FIspace Features – Release V0.16.0

3.3.8.1 List of features by target audience

The following list was elaborated by target audience. It presents the list of features for the version v0.16.0 related to the category of component that provide the GUIs (Graphical user interface) available for each target audience such as the End-users using the front-end, the apps developers using the SDK FIspace Studio tools to design, create and test their apps, the business architects using the tools to design and configure their business process.

Table 1: FIspace features by target audience – Release V0.16.0

Global Feature category Main group of features included

Business Collaboration (End User)

Business collaboration (End User) FIspace User GUI Front-End

User registration

User login

User Profile (public / private) management

Business & Social networking - notification, email, chat / message, news

Business & Social networking - Follower, Likes

Business & Social networking - Reputation / Recommendation / Suggestion

Business & Social networking - Friends / Companies suggestions

Business & Social networking - Basic User Analytics, measurement of profile completed

GUI customization - Themes

GUI customization - Languages customization

GUI customization - Enable / Disable features)

Account management

OAuth client management

Roles management (application developers, business architects, end users)

Company Profile management

My Community management

FIspace 11.11.2015



Partnership management

Advanced search (User, Company)

Guided Tour, Help

Help (Front-End functionalities)

Personal Kanban for task management

Geolocation integration mechanism (for user location)

GUI - Business Process (Template) management

GUI - Capability management

User GUI to access Application dashboard for Apps management (Wirecloud GUI)

User GUI to access Store / Apps Offering (WStore GUI)

Channel & Trigger management (GUI) - Capabilities mapping with Business processes

GUI and visual improvement (usability)

Developers Zone depending on the roles

FIspace Apps developers Integration and tools

FIspace Apps developers Integration and tools FIspace SDK & tools (plugins and studio)

SDK Apps Integration Tools based on Eclipse Plugins

SDK Apps development Tools - Project template

SDK Apps development Tools - Archetype

SDK Apps development Tools - Project Wizard

SDK Apps development Tools - Import / Export tools

SDK Preferences, perspectives, testing facilities,…

Converter and Data transformation tools

Security feature related to OAuth client administration (using secure access to FIspace platform and using pub-lic/external API, based on OAuth 2.0)

SDK Upload Publish Apps / Widget

FIspace 11.11.2015



Access to B2B - BCM Authoring tools (ACSI for BCM)

Access to B2B - EPM Authoring tools (Proton for EPM)

SDK - BCM Configuration Wizard and BCM Configuration deployment

SDK System Data Integration testing tools

SDK Connectors API (capabilities) for Apps and Data integration for several programming languages (JavaS-cript, PHP, Python, .NET)

FIspace Studio (all in one executable)

Business Process definition and integration (Business Architect)

Business Process design, definition and inte-gration (Business Architect)

FIspace B2B environment and tools for Apps developer and business architects

B2B BCM Authoring tools (ACSI)

B2B BCM Engine and integration in FIspace platform

B2B EPM Authoring tools (Proton)

B2B EPM Engine (CEP) and integration in FIspace platform

B2B API to deploy BCM configuration

B2B API to deploy EPM configuration

FIspace 11.11.2015


3.3.8.2 List of Features by FIspace Components

The following list was elaborated by underlying component without graphical user interface necessary to provide the internal functionalities, providing the neces-sary API to interact with external entities and internal interaction between FIspace components. It presents the list of features by internal and underlying compo-nents for the version v0.16.0 related to the category of component that provide the API and technical elements involved in the FIspace platform.

Table 2: FIspace features by FIspace Components – Release V0.16.0


Security (SPT) and Administrative Intermediate Layer (AIL)

Security (SPT) and Administrative Intermedi-ate Layer (AIL)

FIspace platform security based on Security, Privacy and Trust (SPT) integration

Register user

Login User

IDM integration (based on open source software)

SSO (FIspace components and FIWARE GEs)

Access control management

Secure External / Public API

AIL Internal API (using cloud service bus technology)

AIL - Security functions (abstract IDM implemented and integrated)

AIL - Administrative functions (Company, Roles, OAuth client)

Support functionalities and operations (get user info,...)

Secure access by HTTPS / SSL and Certificate

Store, offering, marketplace

Store, offering, marketplace Store management to publish and upload Apps Widget

FIWARE GEs integration related to the FIWARE WStore GE dependencies (Wirecloud, Repository, Marketplace)

WStore GE Integration

Repository GE Integration

Marketplace integration

FIspace Store component enabling store functionalities

FIspace 11.11.2015



Secure FIspace Store component and FIWARE GE dependencies

Store API to Upload / Publish Apps as Widget

Default Payment mode - Free

Store API to validate and deploy BCM configuration

Store API to get and check / validate information of service items per users (e.g. capabilities by user)

System Data Integration, External / Public API for Apps developer

System Data Integration (SDI), External / Public API for Apps developer

SDI External / Public API for Apps developer

Secure SDI API (OAuth client 2.0)

Access to B2B-BCM functionalities / features (deploy BCM configuration)

Access to B2B-EPM functionalities / features (deploy EPM configuration)

Access to Store functionalities / features (Register, Upload Apps,...)

Registry management for Capabilities and Business process

Relationship management between Capabilities and Business process

Relationship management between Event processes and Business processes

Channel and Trigger capabilities / features (sensor data streaming)

Facilities to integrate Apps Domains (message, data,…)

Operative environment - Composite Service Bus (CSB)

Operative environment - Composite Service Bus (CSB)

FIspace Enterprise Service Bus based on Composite Service Bus (based on Cloud Service Bus technology - component open source)

Technical infrastructure supporting Cloud Service Bus (CSB) for internal communications

Queuing management (Messaging service with persistence)

Message expiration management

Publish/subscribe management

Synchronous Request / Response

Asynchronous Request / Response

FIspace 11.11.2015



Message domains (Multi-tenancy support, separation of messaging resources in different domains)

Basic High availability

Basic Monitoring Service

Basic CSB Monitoring

Monitoring infrastructure resources/hosting

FIspace 11.11.2015


3.4 Application Potentials – FIspace Pilots in Detail

By nature, trials in the Agri-Food and Transport and Logistics domains are not bound to one geographical location since they focus on moving goods from production sites to end users. However, the experimenta-tion infrastructure for each early trial involves some key stakeholders that are located in specific countries as represented in Figure 20. These use case trials were conducted in a linked fashion utilizing shared infrastructures where possible to demonstrate the cross domain/use case capabilities of the FIspace and the supporting FIWARE GEs.

Figure 20: FIspace use case trial experimentation sites

Based on the needs of the use case trials themselves, different Apps for the FIspace were developed in order to perform the trials/experiments, and test/validate the features and business model of the FIspace at the 8 use case trial experimentation sites. The following sections present the trials as well as the de-veloped software applications in relation to the trials, addressing various challenges of farmers, growers, transporters, retailers, service providers and many more.

3.4.1 Trial 1 – Crop Protection Information Sharing

Numerous stakeholders contribute to the food on consumers’ tables: suppliers of crop protection material, farmers growing crops, processors, and retailers. These stakeholders have at present independent, most-ly proprietary solutions to supply each other and the consumer with information. Transparency and fluid information transfer is lacking.

There is a great need for tracking and tracing information about inputs, including crop protection agents and the quality of food. This is relevant for consumers’ food awareness and, in case of food emergencies, for a rapid response. Many sources of information are also required to support farmers in decision-

FIspace 11.11.2015


making, for example on the application of plant disease agents. FIspace will connect stakeholders along the agri-food supply chain, enhance license agreement orchestration, and enable seamless creation of different tailored services for, and amongst, stakeholders.

The trial demonstrates the use of Future Internet technologies with functionalities to address social, busi-ness, and policy objectives (e.g., optimization of the use of plant protection agents), create environmental benefits, transparency, and food security. Protection of potatoes against Phytophthora, which requires at present approximately ten spraying actions, will be used as a first use case for this trial.

The Future Internet provides possibilities for real-time support for farmers (Figure 21). Real-time weather information from sensors and rain radar will be made available and integrated in real-time, as will medium range weather forecast. Phytophtora development will be forecasted based on this information and data on cropping history and crop development. A disease warning will be generated should analysis indicate that this is necessary. Recipe formulation with the optimal type of crop protection agent, scheduling of the operation with respect to weather conditions and resource availability and task formulation will start as soon as a disease alert is given. The actual measured crop density is used for real-time dose adjustment based on parameters determined during recipe formulation. Actually applied dosages, sensor information and machine status will be logged and made available by IoT sensors. Sensor data will thus be available for real-time situational support as a service in the cloud, and may even be offered to the public, e.g., by providing information on recently treated fields for hikers with allergies in the form of a “Spray Alert for Hikers” App. Data from such remote monitoring can also be used for fault diagnostics and tracking and-tracing purposes by authorised users.

Figure 21: Layout Crop Protection Information Sharing Trial

The trial is set up by four partners: DLO-ASG, as trial leader, will add new information requirements to the reference model for arable farming, mapping this on the Object Storage GE. Weather forecast, rain radar data and data from soil and weather sensors will be made available following the Publish and Subscribe mechanism. Scheduling algorithms for field operations are made available as a SaaS solution. DLO-PRI will make algorithms for disease warning and recipe formulation available as a SaaS solution. Their algo-rithm for real time dose adjustment will be implemented by Kverneland as a Resource on an IoT Device on the tractor-sprayer combination. DLO-PRI evaluates the overall effectiveness of the Crop Protection Information Sharing concept. Kverneland provides the IoT Devices for Task Control, Tractor, Spraying, and Crop Sensors, which use the ISO11783 communication protocol (ISOBus). A Gateway is to provide information for the IoT backend and Object Store. Several Generic Enablers such as Security, Privacy and Trust and System and Data Integration are used. AgroSense, will realize Task Formulation and take care of all the required Client interaction with the FIspace platform.

For the execution of the trial five farmers are involved (vd Borne, PPO, Wage, Claassen and KMWP) from which three will evaluate the whole Crop Protection Information Sharing concept. These farmers are pio-

FIspace 11.11.2015


neering in the application of modern ICT technology and Precision Agriculture and are an important source of information for farmers that intend to adopt these technologies.

Kverneland and DLO-ASG participate in ISO working groups for standardization of Electronics in Agricul-ture. The results of this Smart Crop Protection trial will thus lead to drafting updates and developing new standards, such as for wireless communication. This provides a basis for wide spread use of FIspace services. Fleet Management, Job Control, Remote Machine Diagnostics and even Environmental Control by auditing agencies are logical extensions and possible apps for the open call in the third phase of the FI PPP project.

Crop Protection Information Sharing Software Applications

The Crop Protection Information Sharing trial demonstrates the cooperation of different providers of in-formation and services for optimal crop production control. This is demonstrated for Phytophthora (Late Blight) control in potatoes by cooperation of the AgroSense Farm Management Information System, the Bo-Mo weather bureau, a Phytophthora advisory service provided by DLO-PRI and a Kverneland Task Controller for agricultural equipment. This minimal configuration for Phytophthora control can be expand-ed by Apps that determine workability, take care of scheduling or provide sensor data.

The following software applications were developed:

Weather Scenario App, providing high resolution weather data for agriculture.

Workability Data App for spraying workability periods based on gathered weather forecast.

Scheduling App for an automatic scheduling of your farm operations.

3.4.2 Trial 2 – Greenhouse Management & Control

All businesses seem to be different when their activities are looked at in detail. What makes the integra-tion from separate entities into one generic entity with smaller entities, related to each other, is the appli-cation of a logical framework that provides useful abstractions from the particular to the general. Seem-ingly unrelated activities, such as terminal management, farm operations and greenhouse operations, become common under such a framework, which also allows them to be supported general purpose Fu-ture Internet and Business Collabortion services.

Figure 22: Greenhouse Management & Control Trial overview

The Greenhouse Management & Control trial involves several Business stakeholders collaborating via FIspace platform in order to accomplish specific business scenarios. The scenarios concern a State Agency for Agricultural Policies, existing Greenhouse and Farm Management Information Systems, which use sensor equipment in Greenhouse environments, meteorological base stations, one Product Tracea-bility Platform etc.

FIspace 11.11.2015


In the context of the particular trial several scenarios are involved, all of which will be executed in order to demonstrate various aspects of the Business-to-business functionality that FIspace will provide. Legacy systems like the ones mentioned above will be integrated into the FIspace so that they are able to inter-connect and exchange information. The different scenarios to be executed are:

Advice Request

Contract search

Managing complaints

Product recall

Task Planning

Greenhouse Management and Control Software Applications

Although seemingly, ICT and Agriculture originate from disparate human needs. The first domain proves to be of upmost significance to the second, in order to facilitate modern complex business processes related to agriculture. The Greenhouse trial aims at providing to the agri-food related business stakehold-ers new means of taking advantage of their legacy systems by integrating them into an end-to-end solu-tion, the FIspace platform.

The scope of the trial is the enhancement of greenhouse management and control operations in order to increase agricultural productivity and revenues as well overall facilitate the diverse food chain business processes.


Greenhouse Crop Monitoring – Crop management consulting at your finger tips!

Greenhouse Crop Analyser – Crop problem diagnosis on the cloud!

Greenhouse Monitoring & Advice – Monitor your greenhouse conditions and receive real-time advice and actions!

Search for farmers app (Marketplace Operations) - Make new collaborations, search for offers, submit your demands, all in one place!

Complaint Management app – Make your customers happy by handling their complaints in an efficient way, analyzing them and solving them once and for all!

Product Recall app – This application allows customers to see if a particular product and LOT has been recalled for food safety reasons.

3.4.3 Trial 3 – Fish Distribution and (Re-) Planning

The Fish Distribution trial is concerned with the planning of logistics and transport activity in the fish in-dustry, a crucial process for ensuring performance across the whole supply chain. The main challenges addressed are low predictability and late shipment booking cancellations, mostly due to lack of collabora-tion or access to information, affecting directly the resource and asset utilization of service suppliers. Fur-thermore, data quality at the planning phase is essential for enabling effective monitoring of transport execution.

The trial will be built on the export of fish from Norway (see Figure 8). Fish exporters produce fish contin-uously, sell it to retailers/wholesalers overseas, then contact a cargo agent for carrying out the logistics operations, including planning, booking/contracting of transport services, customs declarations, follow up, and tracking and tracing of cargo.

FIspace 11.11.2015


Figure 23: Layout of Fish Distribution and (Re-)Planning Trial

The trial show-case the innovations of FIspace by addressing the following key activities in the supply chain:

Distribution (re)scheduling: For the shipper, this includes finding a transport supplier, creating a shipment order, developing a transport execution plan, and rescheduling transport in case of de-viation.

Transport demand (re)planning: For the carrier, this includes demand planning/prediction, re-source management and (re)planning of transport operation in case of deviations.

Tracing of cargo: tracing of cargo at product level is essential for monitoring of transport, but also for detecting deviations at the planning phase (delayed cargo).

The trial explore applications that can contribute to B2B collaboration for improving logistics operations, but also enabling open innovations. Two examples of test applications are:

Improved Booking Reliability: improved upstream planning so that the carrier gets more visibility, more reliable booking, and early notification of changes. The trial will demonstrate how a better integration of the supply chain, in terms of information distribution and accessibility, can contrib-ute to better planning and resource utilization.

Handling of Late Cancellations: provide to the carrier quick access to online e-market place and ability to reschedule bookings, find replacement cargo or additional last minute cargo in a shorter time window compared to what today's IT network can offer. Combined with pricing policies that encourage early booking and dissuade late booking cancellations, this solution is believed to have a strong positive impact on capacity utilization as well as cost efficiency, especially for the short sea shipping spot market.

The scenarios will feature primarily the carrier (container shipping operator) and cargo owners (fish ex-porters) or, alternatively, cargo agents. They will represent real-life situations, business activities, or types of events, and show how FIspace enables them to interact more effectively to increase supply-chain effi-ciency.

SHIPPER (FISH EXPORTER)

CARRIER(SHIPPING LINE)

TERMINAL PORT CUSTOMS

Business Services & Contract

Management

Real-Time Monitoring /

Exception Handling

Transport Planning Service

SOFT

SHIP

E-Market Place(s)

Transport capacity

Transport demand

-IMPORTERS-CONSUMERS

Market information

Demand predictability

-Events-Deviations from plan

BookingCancellation

Booking/cancellationReplacement cargo

Tracing offish cargo

NR

Au

ksjo

n

Info. exchange

Cloud application

cSpace Apps

Back-end systems

FIspace 11.11.2015


The business stakeholders in the trial represent the carrier and shipper sides, and the trial will focus on how collaboration and integration among them. MRTK will coordinate the trial and be involved in devel-opment of the applications. The main project partner is NCL, one of Norway's largest short sea shipping companies, with a large network of fisheries and fish exporters/traders.

Fish Distribution (Re-)Planning Software Application

Fish Distribution Planning is a critical issue in the freight forwarding industry. Main challenges are low predictability of transport demand and late shipment booking cancellations. The Fish Distribution Planning Trial is about planning of transport operations, and builds on the interaction between shipping line and their customers. The business interaction model using the FIspace collaboration platform describes how ship operators can better anticipate cancellations and search efficiently for replacement cargo on the e-market place, while cargo owners can benefit from easier booking process, real-time information and benchmarking of transport services.

The following software application was developed:

CargoSwApp for match-making between transport offers and demand made easy.

3.4.4 Trial 4 – Fruit & Vegetables Quality Assurance

The network of interconnected stakeholders in the ‘Fresh Fruits and Vegetables Chain’ includes the fol-lowing stages of the food chain (Figure 24):

Figure 24: Principal organization of the FFV food chain.

Starting from production on farms, products are collected by traders (often organized as farmers’ cooper-atives), and sold to retail which might involve procurement centers that are responsible for sourcing, dis-tribution centers that collect products from different sources and allocate them to different retail outlets, and retail outlets organized as e.g. supermarkets that provide the link to the consumers as the final cus-tomer.

The organization of this network is supplemented by laboratories linked to farms and traders that provide food safety and food quality analysis, logistics providers that provide transport, service providers that provide re-usable packaging (Returnable Transport Items, RTIs) in form of crates and pallets, and certifi-cation services that provide guarantees on food safety and quality.

The trial has identified some stakeholders for the various stages of the food chain that are ready to get engaged in the formulation and evaluation of the prototypes from a business perspective.

Fresh Fruits and Vegetables Software Applications

Perishable products such as food and vegetables impose very challenging demands on the management of its supply chains. Besides that dynamically changing groups of stakeholders with different and most often incompatible IT systems are involved. At the same time retailers and consumers are demanding more and more data about their food.

FIspace 11.11.2015


The FIspace platform addresses all these challenges with its innovative Business-to-Business Collabora-tion Core (B2B Core). The B2B Core enables an easy and secure data exchange along complex net-works with dynamically changing business partners. By sharing and reusing digital data all stakeholders along the supply chains can massively reduce their process costs. Interoperability is there by achieved by the usage of standardised and already adopted master data, like the GS1 GTIN. Furthermore FIspace Apps provide an immediate setup and usage with minimal related costs. In addition the available Apps PIA, BOXMAN and RISKAN are already providing a comprehensive coverage of needs of food supply chains.


BOXMAN – Easy as Online banking – management of returnable transport items from several pool management organizations.

RISKMAN – Don`t miss any more information regarding critical food issues.

PIA (Product Information App) Product Information exchange – simple but powerful information exchange along the B2B supply chain

3.4.5 Trial 5 – Flowers and Plants Supply Chain Monitoring

This trial is concerned with monitoring transport and logistics processes and focuses on the tracking and tracing of shipments, assets and cargo, including quality conditions and simulated shelf life. The trial will demonstrate the continuous monitoring, control, planning and optimisation of business processes based on real-time information of real-world parameters. The experiment will test, in particular, dynamically up-dating rich virtual profiles of products, containers and shipments, providing multiple views for distinct pur-poses of usage; the combination of different types of sensor data; a timely and flexible availability of product and quality information to a variable network of downstream and upstream partners; and proac-tive control of distribution activities (i.e., triggering deviation management and planning).

The scope of the trial will demonstrate FIspace functionalities regarding:

Cargo and Asset Quality Tracking (“intelligent cargo”): monitoring and control of quality status of the cargo and related assets and its relevance for customer’s quality requests; communication of monitoring results to stakeholders;

Shipment Tracking (“intelligent shipment”): monitoring and control of shipments from (primary) producers to end customers, and specification of its relevance for customer expectations;

Lifecycle Information tracking on cargo characteristics along the supply chain: information collec-tion and distribution along the whole chain ensuring correct information on the cargo accessible for any stakeholder involved in the products’ lifecycle and especially consumers as the final cus-tomers.

Figure 25: Layout of Flowers and Plants Supply Chain Monitoring Trial

FIspace 11.11.2015


The trial is aligned to the flowers and plants supply network (see Figure 10). This sector is characterised by high uncertainty of both demand and supply. Supply uncertainty is high because product is vulnerable to decay, weather conditions, pests, traffic congestion and other uncontrollable factors. Further, demand uncertainty is high because of weather-dependent sales, changing consumer behaviour, and increasing global competition. This results in high variability of supply capabilities and demand requirements in terms of volume, time, service levels, quality and other product characteristics. As a consequence, the timely, error-free and flexible monitoring of products, assets and shipments is a key challenge in floricultural sup-ply chains.

Europe is the leading producer of flowers and plants in the world. Within Europe, The Netherlands is by far the largest producer, accounting for approximately 40% of the total production value. For this reason, the trial experiment will focus on Dutch floriculture. It will include the main supply chain stakeholders, i.e. growers, traders (including wholesalers, exporters, and importers), auctions / producer organisations (in-cluding FloraHolland, the world’s largest flower and plant auction), transporters, suppliers of Logistic As-sets (containers, crates, etc.) and retailers. These supply chain business partners are involved via FLO-RECOM, which is an active industry association for supply chain information in the Dutch plants and flowers sector owned by the auction house FloraHolland (growers cooperative with about 6,000 mem-bers), the Association of Wholesale Trade in Horticultural Products (VGB) and the Trade Council Agricul-tural Wholesale Trade (HBAG). DLO-LEI will act as coordinator and technical architect of the trial. DLO-FBR will contribute by delivering quality decay models as a service.

Flowers and Plants Supply Chain Monitoring Software Applications

The management of product quality is of vital importance in supply chains of fresh produce such as flow-ers and plants. This trial demonstrates the possibilities of Future Internet technologies for dynamic Quality Controlled Logistics in floricultural supply chains. The trial system will provide practical functionalities in particular for real-time access to quality information including ambient conditions (e.g. temperature), early warning in case of deviations and prediction of remaining shelve life.


Botanic Info App – always and everywhere the availability of flowers and plants at hand.

Quality Prediction in the Horticulture chain – Predict the quality of a plant at specific points in the chain using environmental data in the history of the plant.

Quality App – Real time, chain-wide insight in flowers’ and plants’ current quality.

Supply Chain Quality Monitoring App – Quality monitoring of flowers and plants: real-time and ongoing from grower to retail.

3.4.6 Trial 6 – Meat Information Provenance

At present, there are several systems that provide meat consumers with what is sometimes called rich information on meat. This includes the origin of the meat, meat type, company and date of slaughtering and further processing of the meat item bought by the consumer at some supermarket or other retailer. Several systems also extend this rich information to recipes on how to prepare the specific meat item. Consumers have already indicated that they want even more reliable information (i.e. certified by accred-ited bodies), such as information on sustainability aspects of the meat supply chain, animal welfare and health aspects. Examples of information related to human health include information on allergenic charac-teristics, chemical additives and how to prepare that specific piece of meat.

During the last two years within FI-PPP Phase I project, SmartAgriFood, such a system is tested in a BonPreu supermarket in Barcelona, Spain and implemented in several German supermarkets (e.g. Aldi-Nord, Aldi-Süd, Lidl, NORMA, Aldi NL, while Germans largest supermarket EDEKA is working on it). Fur-thermore, in other countries (e.g. US, Japan, Australia) similar systems are and will be developed. With the German system, consumers can get a substantial part of the information they want on meat. But the system is also restricted, as it is very cumbersome to scale it up and, moreover, it serves consumers only, while considerable effort and costs are for the meat supply chain partners. In case of food alerts (e.g. BSE, horsemeat scandal, aflatoxine, dioxine) tracking & tracing is very difficult, as passing of information (from farm to retailer and from retailer back to farm) is based on the principle one-step-back, one-step-forward, which means that every meat supply chain partner is enforced by regulations to know where his input comes from and where his outputs go to. Reconstructing the flow of information is a giant task and can take up to several days, e.g. in the horsemeat scandal several days or even weeks. Any response to such a meat alarm is not only slow, but also very imprecise, concerning too much meat of too many sup-

FIspace 11.11.2015


ply chain partners. In contrary, in case of a meat alert ICT should enable a fast and surgical response in case of meat alert. Not only tracing of meat, as in the horsemeat scandal, is difficult, but other examples of imprecise response are related to tracking: e.g. prohibitions to export, or to deliver, or to transport or to produce. Moreover, with the existing system information is stored and transmitted in all kinds of formats, following various standards. Meat supply chain partners cannot use this system to optimise their busi-nesses and to respond to wishes of their supply chain partners and meat consumers.

In the new meat supply chain information system the MIP trial will improve the functionality for consumers and add several new functionalities for all supply chain partners. The new system will be based on the EPCIS standard (Electronic Product Code Information Service). All meat supply chain business process-es will be stored in one or more repositories that are designed to store EPCIS events. EPCIS is a widely used standard for food and other products. Basing the new meat supply chain information system on EPCIS enables providing instant information on where all meat items are at any time in case of meat alerts. Furthermore, the system supports generating a list of all sources of meat safety issues, related to the meat alert.

In the MIP trial the end-result will be a reference architecture for a new meat supply chain information system that is tested and ready to be rolled out in FI-PPP phase 3 projects, as depicted in Figure 261. Furthermore, the trial will build a community of meat supply chain stakeholders to involve them and pre-pare them for extending the functionalities and to provide more information that is interesting for meat consumers and all stakeholders involved, including authorities and the society in general.

info

rmation

SC

part

ners

pro

ducts

third p

art

ytr

aceabili

ty p

rovid

er

farm slaughterhouse meat processorpackager &

distributorretailer

farm management

information

system

slaughterhouse

information

system

meat processor

information

system

packager &

distributor

retailer

information

system

consumer

smartphone

PC

static data repository

EPCIS repository dynamic datainternet

EPCIS

events

EPCIS

events

EPCIS

events

EPCIS

eventsinfoquery

EPCIS

events

server software

cow quart batch packed QR item

QR-code

Figure 26: Reference architecture with the core parts to be implemented and tested in FIspace’s MIP trial.

Not only the MIP trial will uses EPCIS as an enabling technology but also the fresh fruit and vegetable quality assurance trial and the flowers and plants supply chain monitoring trial.

Meat Information on Provenance Software Applications

Easily obtaining full information about a piece of meat in the supply chain up until the consumer in a su-permarket is still a wishful thinking. This trial aims at ensuring meat supply chain parties, regulators and consumers to have accurate information concerning where a meat product originates from (production farm) and his history along the meat supply chain.


FIspace 11.11.2015


Farm Capture App – No need for an expensive Farm Management Systems to take part in chain-wide meat transparency.

Query App – Query detailed transparency information of your meat.

Discovery App – Where are all the event data stored?

Aggregation App – Supply chain parties and authorities/regulators want concise but full infor-mation on meat.

Consumer App - Do you know what you buy?

3.4.7 Trial 7 – Import & Export of Consumer Goods

The import and export of consumer goods trial addresses a supply chain network which can be differenti-ated by several dimensions; by the nature of the markets (i.e. consumer expectations in the markets), by product ranges (relative importance i.e. priority of a product in that specific market), by sourcing types (production or trading) and also by the agreements and the content of the business done in collaboration with transport service providers and their capabilities. International transport is always constrained by the laws and enforcements by the legal authorities (i.e. customs), however impact of such mechanisms on the business flow will not be included in the scope of this trial.

Figure 27: Layout of Import and Export of Consumer Goods Trial

As depicted in the figure given above, the process starts with a procurement order of raw materials from a material supplier located in the far-east and inbound transportation of the materials to the facility of Arcelik where they will be transformed into finished goods that in turn will be exported as consumer electronics goods to the UK.

The trial includes operational planning of logistics activity in line with the existing production plans (for inbound) and promises to customer (for outbound), purchasing/planning of logistics operations and the timely monitoring and coordinating the execution of the transport activities. The trial can easily be scaled up to the total supply chain and also other supply chains in Phase 3.

End-to-end collaborative supply chain planning, along with the enhanced visibility, is essential. Linking demand with supply throughout the entire supply chain is required for implementing tailor-made supply chain strategies in order to increase reliability and responsiveness to customer with a cost efficient and high quality manner. Cloud-based collaboration services and apps can lead to wide acceptance with a large number of small suppliers and dealers, as it significantly reduces the investment in such IT.

The trial focuses mainly on two main processes:

E-Planning process addresses the challenges encountered during the operational planning of the transport activity from the view point of a manufacturer. Scenario mainly focusses on the manage-

FIspace 11.11.2015


ment of the transport service, i.e. transport order & booking and organizing the execution of an in-bound process for Arcelik. The story is built planning of the transport of materials in collaboration with the material suppliers and transport service providers. Cloud-based collaboration services and apps allow a better visibility and potential to reach out new potential partners for collaborating without heavy manual intervention. Potentially it is expected to increase the visibility of SMEs in global busi-ness collaboration. Increased visibility of the processes and automated notifications for deviations can lead to a more intelligent supply planning which lead to more effective supply chains.

Automated shipment tracking process mainly focuses on the process of shipment status monitoring and timely deviation handling with automated notifications and triggers for re-planning. The scenario starts when the materials to be used for production leaves Arcelik’s warehouse located in Turkey and continues till their journey to their end destination in UK. The transport chain planning and optimisa-tion with effective and proactive deviation management is necessary to ensure effective production planning, on-time delivery in full and high on shelf availability at the destination with high customer satisfaction level. The trial will explore the benefits of future internet applications that can provide “fast and seamless” real-time information sharing through one channel and increased level of interaction between involved parties.

Import and Export of Consumer Goods Software Applications

In Transport & Logistics – by nature working in collaborative business networks – every stakeholder needs to know the actual status of the ongoing transport processes to properly control the respective business activities and efficiently handle often occurring deviations. This requires end-to-end visibility and seamless collaboration in logistics business networks, which can be realized on top of novel technologies for data, document, and process sharing on the cloud.

The trial is concerned with the planning and execution of logistics activity in the consumer goods sector ensuring effective planning of the related activities resulting in improved coordination, loss minimization, efficient use of resources and high customer satisfaction level.


Shipment Status Application – Improved end-to-end supply chain visibility.

Manual Event & Deviation Reporting Mobile Application for seamless status & deviation re-porting.

Transport Demand Application (TD) for visibility over the transport unit.

3.4.8 Trial 8 – Tailored Information for Consumers

The aim of the TIC trial is to test and present how we can use all the potential of Future Internet and the FIspace platform to improve food awareness among consumers. For this experimentation, we will focus on developing a trial system that will help the consumer to be more aware of the food they buy in the su-permarket and that they eat.

The main challenge is the capability to collect information from the cloud, from different providers and not from a central information repository, in order to furnish an open platform with all the gathered product data from several points of the supply chain, and provide innovative functionalities by means of FIspace Apps.

The TIC trial is mainly focused on the data management and provision to consumers. There are two main information dissemination approaches:

The push approach, which enables the retailer to make the consumers aware of information con-sidered relevant for them.

The pull approach where consumers get tailored information of a product before/during and after their shopping and getting only the product attributes of their interest according to their consumer shopping profile.

In this Phase II, we will implement the Phase I functionalities (providing tailored product information) into the FIspace ecosystem and include additional features related to:

Push Information Approach.

Consumer feedback

Augmented reality applied to providing tailored information.

Shopping list management.

FIspace 11.11.2015


Transform data into knowledge based on semantic rules.

Food Safety alerts.

These functionalities are described in the following user story:

Carl is a frequent shopper at Plus Fresc and he has Plusi fidelity card. He has received an email inform-ing that Plus Fresc forms part of a new platform called FIspace that offers an App store where he can get/buy different Apps that offer new innovative functionalities.

Carl is allergic to wheat, and cares quite a lot about his weight, although he loves making desserts. Since now they are three at home he has to care about product price and tries to benefit from as much offers as he can.

Carl logs himself in the FIspace platform and accesses the store. He decides to download the PRODUCT INFO App, since each time he enters the shop he spends lots of time looking for products that are gluten free and this App will allow him not only to know which product are gluten free, but to get detailed product information by just scanning the QR code placed in the product). This information can include social, health or environmental aspects. There is also the possibility to scan those quality logos the product pro-vides and obtain their real meaning, since sometimes it is a bit confusing. He enters the App and config-ures his profile, introducing the type of information he want to get, the preferred language, etc and the fidelity card number. He downloads also the TRAFFIC LIGHT App that will allow him to visualize with easy color codes the fat, saturates, sugar and salt of the product, based on the Food Standards Agency rules:

Table 3: Example „Traffic Light“ app information

per 100 grams low (green) medium (amber) high (red)

fat ≤ 3,0 gr. > 3,0 gr. and ≤ 20,0 gr. > 20,0 gr.

saturates ≤ 1,5 gr. >1,5 gr. and ≤ 5,0 gr. > 5,0 gr.

sugar ≤ 5,0 gr. > 5,0 gr. and ≤ 12,5 gr. > 12,5 gr.

salt ≤ 0,3 gr. > 0,3 gr. and ≤ 1,5 gr. > 1,5 gr.

So as not to buy unnecessary products, Carl wants to prepare his shopping list before going to the su-permarket. He is about to start writing it down when he remembers the FIspace platform, he enters and realizes there is a SHOPPING LIST App, and this App allows him, not only to make his shopping list by selecting the product, but by scanning its code, so he scans those products he has at home. He cannot forget to buy the ingredients of the cake for the birthday of his little daughter! But, did he need milk or cream? He enters the SHOPPING LIST App and accesses the recipes, he looks for the chocolate cake recipe and adds the ingredients to his shopping list. He realizes he can add products to the shopping list by family and subfamily categories. Therefore, he adds cream and the chocolate all his family likes the best; Plusfresc own branded 70% cocoa chocolate.

Now Carl is ready to go to the supermarket. Once he arrives, he sees a big banner announcing that cus-tomers can improve their shopping experience by FIspace innovative functionalities. He is ready to begin his shopping. Along the aisles, he finds products with a QR code. He reads QRs with his mobile, and through the PRODUCT INFO app he receives tailored information about the products he scans.

Finally, Carl reviews the shopping list and he ticks a box next to each product to be sure he has bought all of them. Unfortunately, Carl does not realize he has forgotten to buy rice. He validates his shopping and immediately the mobile beeps indicating he has missed the rice. Goodness! His wife was going to cook a paella for the birthday party and he could not forget this important ingredient.

Once Carls finishes his shopping he goes back home, and when he opens the milk, the taste is very strange, so he decides to send this complaint through the PRODUCT INFORMATION App. In few days, he receives an answer from Plusfresc thanking the feedback and including an e-voucher from the milk producer for four free of charge bottles of milk.

The next day Carl goes to the supermarket he sees a new banner announcing “AUGMENTED REALITY OFFERS”. What is that? Carl enters the FIspace store and discovers the AUGMENTED REALITY App. He downloads it, and when he enters, he receives a message saying “Today special offer in cereals” information Plus Fresc has predefined that the consumer will receive (in a “push” mode). Following the instructions in his mobile, Carl directs his mobile to the cereals and gets information about offers super-posed to the image he is getting.

FIspace 11.11.2015


A couple of weeks after, he is at work and receives an email informing there is a security alert related to some tomatoes he has bought, so he is required to get them back to the shop in his next visit so as to give him his money back.

Tailored Information for Consumers Software Applications

In consumers’ everyday shopping experience, awareness of the origin, harvesting and conditions of their purchased products is still limited. All that, while the complexity of where our food comes from, what it contains and under which conditions and additives it was produced, increases. Tailored Information for Consumers is thus part of the FIspace ecosystem with the focus on developing a system that helps the consumers to be more aware of the food they buy in the supermarket and consume every day.

The main challenge is the capability to collect information from the cloud This includes different providers and not a central information repository, in order to furnish an open platform with all the gathered product data from several points of the supply chain.

Taking advantage of the 3rd TIC trial Workshop in Barcelona (June 2015), Plusfresc recorded a video showing the activities addressed by the TIC trial as part of the FIspace project. It shows current consum-ers problems regarding product information and how FIspace appears as a tool allowing cross sectional collaboration and transparency throughout the retail chain. The video shows all the functionalities of the apps created by the TIC trial, including images of the workshop and some opinions gathered from con-sumers who tested the apps.


Traffic Light App – All you need to know about the product your trolley.

Product Info TIC – Product Information TIC task is to enable product information.

Tailored Product Info App – TaPIA Know what you eat.

Shopping list & Recipes App – With one click to your shopping list.

Augmented Reality Product Info App – Through different eyes: Learn all you need to know about your favorite product with the Augmented Reality Product Info App.

Push information App – Best discounts at your fingertips.

FIspace 11.11.2015


4 Offering and Support for FIWARE Phase 3 Projects

4.1 Description of technical support

A technical support process has been put in place during the project extension period in order to guaran-tee the continuity, availability and quality of service delivered to developers. The intermediary tool to submit technical issues is Bitbucket, where a separate group has been created especially for phase 3 developer requests. The technical support is provided by the FIspace technical team and issues are raised by the FIspace accelerator channel (FInish, SmartAgrifood, FRACTALS and SpeedUp projects). Thus this procedure serves also the goal of transferring knowledge towards accelerators.

Steps to create an issue:

Create a user account in bitbucket if you do not have one already

Go to https://bitbucket.org/fispace/phase3support/issues

Press the + Create issue link to create an issue

Explain the encountered problem

In the title mention your accelerator project name

Assign the issue to the Technical Support Responsible, which can be found under the user name “first level support fispace” in Bitbucket

The following requests types are identified as valid:

Incident Management of FIspace related issues

Problem management of FIspace related issues

Requests are going to be rejected if:

The raised issue is out of scope of FIspace platform

Requests are submitted directly by developers

Issue Management Steps

Open: After assignment issues receive Open status

Resolved: As soon as an issue is solved change the status to resolved

Invalid: Change the status to invalid in case of issues to be rejected

On hold: Choose this status if the resolution of the issue needs longer period than 72h.

4.2 Bug fixing

Once a wrong behaviour is detected, an issue with type bug must be created in the appropriated issue tracker. The issue must describe the expected and actual behaviour, the description of steps necessary to reproduce again the bug. Depending on the bug visibility, the bug must be assigned to the first line of service (in the case of phase3support) or to the responsible of the environment where it was found (EE or IE) or finally to the CR.

Assigned individual must reproduce the bug and confirm it or reject it by the status invalid.

Once the bug is identified, bug fixing process starts either fixing the bug directly or reassigning the bug to the above environment or more specific CR recursively. Result of the bug fixing process is always a new release. The release can be propagated or install, depending on where it occurs.

https://bitbucket.org/

https://bitbucket.org/fispace/phase3support/issues


https://bitbucket.org/


FIspace 11.11.2015


In terms of planning, bug fixing process does not follow any fixed time frame. However, bug fixing process has a fast track and higher priorities than Change Request.

4.3 Communication of Platform Status

FIspace platform consist of three environments, PIE is for development, IE is for integration activities and FIspace public instance that is used by EE to conduct experiments of Accelerators.

Operational status of PIE and IE will be shared dynamically with corresponding platform module owners and integration leads by the help of hosting monitoring activities. Operational status of the FIspace public instance will be shared with Accelerators for unexpected or expected downtimes.

Unexpected downtime information, with the reason of downtime, will be shared with Accelerator technical leads and developers immediately.

Expected downtime may occur, due to a major release which is planned to occur every month. After the release is accepted by integration team the outcome will be able to be promoted and installed in the pub-lic environment. After this installation process, the platform must pass experimentation test plan and then announcement will be made for the short downtime and availability of the new version.

Another case of expected down time may occur due to an issue regarding to configuration of the public Instance which does not require any development or Integration cycle. Public instance configuration maintenance downtime may occur on weekly basis.

4.4 Operational Hosting of the Platform

Operational hosting of the FIspace platform is based on three major setups

Cloud Infrastructure Setup

Network and Security Infrastructure

Support and security upgrades

Cloud Infrastructure Setup hosts VMs for three different environments.

PIE is for development, IE is for integration activities and FIspace public instance that is used by EE to conduct experiments of Accelerators. All three environments are secured via FWs and will be monitored for network level operation. Support is given to platform developers, integration team and the team re-sponsible for FIspace public instance regarding to Cloud, Network and Security Infrastructure issues. Monthly Down times may occur for solving these issues by informing platform Task leaders, maintenance coordinator and Accelerators in advance.

Zabbix monitoring solution will be used for network monitoring and application monitoring of each envi-ronment (PIE,IE and Public Instance) for default metrics defined for FIspace. Currently, PIE environment is monitored based on availability and performance of certain modules. IE and FIspace public instance will also be monitored regularly. Rules can be defined and email alerts in case of rule violations will be sent to platform component owners and public instance team leaders.

4.5 Assignment of User Roles

In the current procedure, role assignment requests are sent to FIspace and depending on the request, App Developer or Business Architect roles are assigned to a user manually by the leading partner of the Security task. This procedure can be maintained and responsibility may be shared with partners of Secu-rity task and the FIspace project management partner for the requests that will be received from Accel-erators. At the same time a company admin who creates the company using FIspace UI can do the role assignments for the user of his company using the UI. This option currently is not available but it can be implemented in future releases or it can be implemented when platform will be commercialized by the FIspace organization.

4.6 Registering Messages for new capability types

Information exchange between FIspace platform and “out-side” world is based on messages. Those mes-sages have to be defined in the core module of the platform.

FIspace 11.11.2015


Once messages are available at the core module, they can be used by FIspace in form of an entity called Capability Type. In this manner, Capability Types are envelopes or wrappers of the messages to be ex-changed. In the image below, an example of a capability type is depicted:

Capability types are intended to be created by Business Architects, and can be easily defined using the existing tools offered by the platform, i.e. Frontend, SDK or backends.

FIspace initially provides a general set of messages to be used, but it is likely that an organization can defined its own messages. In other to support this registration, FIspace has a well-defined procedure to register new messages in the platform. Those instructions can be found under the “Create a Pull Re-quest” chapter of https://bitbucket.org/fispace/apps/wiki/integration/Open%20Call%20apps%20integration %20-%20First%20%20stage, available at the project’s wiki home page.

Once this process is successfully completed, it is important to highlight that those new messages will be firstly available at the Preliminary Integration Environment. They will not be available to be used by an external audience until they are promoted to the Experimentation Environment. It is the responsibility of the platform operational team of this environment to announce when a new version of the platform is be-ing promoted, and so, when the new messages will be ready to be used.

4.7 Deployment/removal of Business Processes and CEP Patterns

The Business Architect first creates a Business Process Template through the front-end. Then, using the SDK, the starting BCM configuration is created. This can then be imported into the authoring tool, and changes made, and then exported (i.e., downloaded from) the authoring tool. The configuration should be managed in a similar manner to source code; thus it could be stored in a Source-Control Management system. The configuration can then be deployed through the SDK (and later removed through the SDK as well).

The Business Architect should also prepare the EPM Logic by accessing the EPM Authoring Tool through the SDK. This configuration can then be exported from the authoring tool – resulting in a JSON file. De-ployment and undeployment is handled through the front-end. This is done for a specific business pro-cess by editing the JSON to reference the correct queue name, and creating a trigger.

https://bitbucket.org/fispace/apps/wiki/integration/Open%20Call%20apps%20integration%20%20-%20First%20%20stage

https://bitbucket.org/fispace/apps/wiki/integration/Open%20Call%20apps%20integration%20%20-%20First%20%20stage

FIspace 11.11.2015


5 Commercialisation Prospects

5.1 The FIspace Usage Model

As the final part of the FIspace overall design, the following outlines principal usage model of the FIspace. For this, we first define the main processes for using and working with the FIspace, and then define the workflows for the main user groups.

5.1.1 Main FIspace Processes

The FIspace processes define how the features provided by the FIspace shall be used to conduct busi-ness activities. In the context of a comprehensive conceptual overview, we primarily focus on the pro-cesses from the user perspective for using and working with the FIspace; of course, more detailed pro-cesses and interactions between the components are required for the technical realization.

Figure 28: Main FIspace Usage Processes

Figure 28 summarizes the main FIspace usage processes, and indicates the technical building blocks that will realize the respective functionalities. The first process is concerned with two aspects: firstly, all end-users (i.e. experts working for a company) are demanded to be registered on the FIspace, and their accounts with access permissions and app usage are managed on the company level. Secondly, the management of business partners and contacts shall be supported by the FIspace as a single point where all relevant information are available, which is commonly considered as a highly value-adding fea-ture of a business collaboration platform; for this concepts from collaboration platforms from the B2C world (e.g. facebook, google+) as well as from the B2B world (e.g. LinkedIn, Yellow Pages concepts, etc.) will be analysed to provide best-value business network management services without violating confiden-tiality interests of the participating companies. The processes (2) – (4) are concerned with the develop-ment, purchase and usage of FIspace Apps, which shall provide the value-added services for collaborat-ing business networks with integrated collaboration features as outlined in the illustrative example above: at first, a FIspace App is implemented, using the Development Environment; then, it is uploaded to the FIspace Store, where interested user can purchase it, and finally it is set-up for the individual user, includ-ing the connection to existing system landscapes and the configuration for the individual needs of the end-user, e.g. personalization of appearance, notification settings configuration, and the creation of cus-tomized solution by mashing up several FIspace Apps.

While these processes outline the steps for creating and using a single FIspace App, the overall aim is to enable and foster the efficient and seamless collaboration in existing, emerging, and growing business networks. For this, several and an extensible number of FIspace Apps shall be developed for the same

FIspace 11.11.2015


(or at least similar) collaborative business process, so that the participating businesses can constantly extend their partner network and adapt their collaborative IT solutions.

5.1.2 Principal User Groups and Workflows

In order to illustrate outline how the FIspace shall work in more detail, the workflow descriptions in the tables below outline the usage procedures for the following principle user groups of the FIspace:

End-Users: the business experts using the FIspace to conduct the daily business activities, with special focus on their interaction and collaboration with business partners;

Business Process Engineers: the ICT experts (internal or external) that support End-Users in the configuration of the FIspace for their individual business needs, particularly for the definition of customized business processes by using the FIspace Apps and the FIspace’s customization support services (on various levels: company / organizational unit / individual);

App Developers: the software and system providers who offer solutions and applications in form of Apps via the FIspace.

Of course, the actual ecosystem of the FIspace will encompasses much more roles whose respective business interests and motivation need to addressed and supported in order to ensure acceptance in a broader community. Examples for additional roles are e.g. the more detailed separation of the End-User group into e.g. Producers, Shippers, Logistics Service Providers, etc., who will together form the custom-ers and therewith drive the usage of the FIspace; also, several additional roles on the IT-provider side can be distinguished, such as e.g. the Platform Operator(s), Infrastructure Providers, Consultants, and 3

rd-

Party Solution providers.

FIspace 11.11.2015


5.2 The FIspace Business Model

5.2.1 FIspace Business Model CANVAS

The point of departure for FIspace was the business model work conducted in the FI-PPP Phase 1 pro-ject, FInest and SmartAgriFood. FInest is a cloud-based platform for collaboration and integration of enti-ties in the transport and logistic domain. SmartAgriFood elaborated upon six use cases in the areas of (1) Smart farming (including sophisticated and robust broadband sensing and monitoring of animals and plants), (2) Smart agri-logistics (including intelligent transport and real-time logistics of agri-food products) and (3) Smart food awareness (focussing enabling the consumer with information concerning safety, health, environmental impact and animal welfare). Based on this, the following Table 4 presents the merged FIspace business model canvas.

Table 4: FIspace merged canvas

Key Partners Key Activities Value Proposition Customer Relations. Customer Segments

Hosting services provider

IoT hardware and service providers

SW developers, integrators and consultants

Machine and material suppliers

Financial service providers

Industry associa-tions

Standards / Certi-fication bodies

Governments / authorities

Research insti-tutes

End-consumers

Platform management

Platform operations

Service provisioning

Marketing

Continuous improve-ment

Design and develop

Consultancy

Maintenance

Promotion and network-ing

Easier access to larger markets

Ease of use

Cost reduction

Visibility

Increased / new reve-nue, premium prices

Control

New customers

Innovation opportuni-ties

New outlet for services

Improved product /service quality

Wider application of certification and standardization

Tracking / tracing / transparency through supply chains

Increase of trust

Risk reduction

Ease of use, deployment and development

SDKs

Personal support

Online support

Automation tools

Self-service

Information provision / exchange

Robust help

Community build-up

User feedback

Business users, E.g. shippers, farmers, growers, animal producers, manufac-turers, suppliers, logistics service providers, retailers, supermarkets, food processors, traders, crate managers,

End consumers

Government, stand-ard and certification organisations.

Application develop-ers

Advertisers

(Society)

Key Resources Channels

Platform technology

App store

Apps / services

Server infrastructure

Cloud

GEs

IPRs

Information

Trust

Support relationship

Web presence (incl. social media)

Direct sales / Events

Existing networks (e.g. internal sales force, direct marketing, business com-munication, advertising, sector organisations and PR-agents.)

App store / Marketplace

Advertisements

Word of Mouth

Government or industry organisations

Cost structure Revenue streams

Operational costs (hosting, maintenance, support, etc.)

Marketing costs (sales, advertising, acquisition, events, etc.)

Development costs (ICT infrastructure (sensors), SDKs, continuous improvement, training, etc.)

Costs for other partners in the FIspace ecosystem, e.g.

- cost reductions induced by FIspace - costs of using FIspace services and apps - cost for app developers

Membership/Subscription fees (Saas)

Advertising fees

Transaction fees

SDK fees

Sales of Information / Analytics

Consultancy / service fees

Revenue streams for other partners:

HW sales, SW licenses, hosting fees, ICT service, consultancy and system integration fees, charging fees for financial transac-tions

First and foremost the canvas analysis identifies the characteristics of the service the platform has to offer to meet the needs of its customers, i.e. its value proposition. FIspace aims to deliver a number of bene-fits related to (1) better satisfying customer requirements (enhanced monitoring and tracking of goods as they move along the value chain etc.), (2) increase business efficiency and optimization throughout the value chain by (e.g. significantly reducing manual efforts for planning and re-planning) and (3) facilitating new business opportunities (by providing more efficient and transparent service offer management, opti-mizing partner contract negotiations, etc.).

FIspace 11.11.2015


It is the vision that the platform will provide multiple benefits to the business users. In the long-term, and in general, the implementation of the platform should lead to lowering costs and better collaboration be-tween business partners or users (e.g. a shipper that needs to ship goods, a manufacturer who needs material, a farmer that needs spraying advice). When enough business users have subscribed to the platform, they would, whether sellers or buyers, benefit from a greater variety of partners to do business with. Small service providers will particularly benefit since they are able because of the lower investment and the access to an open platform. In addition, ratings functionality and market places will further in-crease the efficiency of markets. Easier customization of business processes, the possibility to pay only ‘per-use’ and automated contracting, service level management and payment services should be estab-lished, which will lead to lower overheads and lower transaction costs (in the broad economic sense). In many cases this will lead to higher product and service quality, throughout the supply chains, in turn en-larging markets, and provide possibilities to charge more and leading higher long-term profitability.

In transport and logistic chains transparency, event handling, event notification, rapid integration to backend systems, and service level monitoring will allow e.g. business users (e.g. shippers) to optimise their (shipment) processes. Lead-times are likely to be reduced in many cases. In general less waste (perishable goods) and better capacity utilization and fewer transport kilometres will reduce costs and increase efficiency.

Provision of expertise can be outsourced or improved internally by automated processes. More advanced and efficient processes will not only lead to economic gains, but also more environmentally friendly pro-duction and service provision. Better visibility and transparency in (e.g. food) supply chains will, among other things, provide opportunities for new revenue streams, but also improve trust (as will higher quality and reliability). Exception reporting will allow taking out products from the chain that are dangerous or of insufficient quality.

Though more objectives are envisioned as well as paths of how to realise these objectives, in its basic form, the value proposition of FIspace would be to support business users through ICT in their various ways to enhance their business. Still this value proposition is quite multi-faceted and in need of showcase examples to concretise and illustrate these benefits. This was one of the aims of business model activity in FIspace, which was conducted in close collaboration with the trials.

However, it is envisioned that app developers shall have access to a large number of business users once a certain (critical) mass of such users is reached. That would lead to economies of scale and gener-ate transaction revenues. Lower development costs and the possibility to mash-up with other applications could also be foreseen and for the moment is part of the envisioned value proposition to app developers.

Some other entities that could (sometimes indirect) profit from the FIspace are defined in addition, e.g. advertisers that profit from views for their advertisement on the platform. Society benefits from environ-mental impacts and better response to alerts and emergencies. Several suppliers of components (e.g. sensors) will benefit from enlarged markets. FIspace may also allow for wider application of standards for standardization- and of certification schemes for certification bodies. Some applications will provide end-consumers with e.g. higher food awareness, tools for shopping, food alerts, which will possibly increase their willingness to pay and trust.

Finally, whoever develops and operates the platform, for now called the platform provider or operator, will be able to capture some of the value provided by the platform. Development and/or management organi-zations can generate new revenue streams through licensing the platform software or operating the plat-form.

FIspace will serve many customer segments, including farmers, growers, manufacturers, shippers, crate providers, logistics service providers, retailers, end-consumers, software development companies, infra-structure hosting companies, traders, systems integrators, hardware manufacturers, facilities companies, consultants, etc. and possibly standardisation-, certification and public organisations while providing value to society at large.

The partners can be structured according to the two markets the FIspace platform operates in. These are: (1) the market that mediates between business users and app developers, and (2) the market that medi-ates between business users as buyers and sellers. The latter is also the two-sided market that an app might intermediate. Thus the core customer segments can be broken down to three main categories (based on FInest):

Business users - ‘buyers’ that needs a service, product or information, and seeks to establish a business relationship with service or product providers (e.g. shipper that needs to ship goods, a manufacturer who needs material, a farmer that needs spraying advice).

FIspace 11.11.2015


Business users - ‘sellers’ that wants to sell a service or product to another business user, e.g. Lo-gistics Service Providers (LSPs) that provide logistics execution services for performing transport operations, or a supplier that provides its product to the next step in the value chain.

Application developers/providers: entities that develop apps (or app components) in conformance with the FIspace platform’s app development requirements. Apps are provided via the FIspace Store.

While this distinction draws on the FInest analysis, which made a clear separation between shippers (buyers) and LSP (sellers), we consider this segregation as an example. This distinction is not applied rigorously for FIspace.

Certainly, apart form the core segments other partners should be considered. The platform opera-tor/provider is not a customer but the supplier of the service that FIspace delivers, whose business this analysis seeks to model. In any case, this will be a company or other entity that operates the platform including the FIspace Store and provides the necessary support and toolkits to app developers and pos-sibly support to the business users. The platform operator may also take on the roles of maintaining and developing the platform and its components as well as hosting it, but other companies could also take up these roles. Exactly which roles the platform operator/provider should take up are still under consideration in the business model task, and will be further discussed in Chapter 5.

Additional partners foreseen includes consultants who support the business users in deploying the appli-cations, financial service providers and, possibly in the future, advertisers that would seek to advertise their goods or services on the platform, public services, standard and certification organisations and soci-ety at large. These could be considered customers of FIspace as well.

FIspace needs to create relationships with these customers. These are of two types of relationships: those with business users and those with application developers. While ease of use, deployment and development is key, FIspace will need to establish close relationships with both. Assistance to the busi-ness users (shippers and LSPs) will be needed during the setup process, for e.g. configuring the system for use, connecting to the backend systems, linking IoT devices, setting up security, customising the user interface and accessing apps. Business process engineers will eventually conduct this. Other relation-ships are required with key partners (see below) that support the business collaboration.

Developers will need support as well, in the form of SDKs as well as personal assistance in learning how to develop and possibly certify FIspace apps and learning about possible app revenue system. Besides personal assistance, this support, can come in many forms including online support, automation tools, self-service and community build-up. Finally, feedback from customers will be key to continuously im-prove the platform

FIspace delivers its value proposition to its targeted customers through different channels. As identified in FInest, these channels needs to be activated for purposes of awareness generation, evaluation, pur-chase, service delivery and support. Awareness generation is already taking place in the FIspace project, and need to continue as FIspace moves to commercialization. FIspace needs to provide business users with incentives, opportunities and support to evaluate the platform by trying out their services. FIspace also need to provide app developers not only with SDKs but also with training, testing and other support services. Even monetary incentives could be envisioned (cf. Phase 3). When the platform reaches a suffi-cient number of users and app developers, and the value of the platform has increased, such incentives can be relaxed.

The channels that can be used range from organising events, web presence (incl. social media), the use existing networks (e.g. internal sales force, direct marketing, business communication, advertising, sector organisations and PR-agents), the FIspace Store and marketplace itself, advertisements, word of mouth and activation of other partners such as industry organisations.

FIspace needs to capture some of the value provided to the customer segments. It needs to create reve-nue streams that are sufficient for all players in the ecosystem or other benefits that justify a cost. The main source of revenue is likely, or will have to, to come from the business users of the platform, who in turn have to be willing to pay because of their perceived value of using the platform. Several revenue models can be foreseen including entry fees, subscriptions, and transaction-based fees. Selling seg-mented information about buyers’ habits is another possible revenue source. FIspace may in principle also generate revenues from sales of software development kits (SDKs), consultancy and training ser-vices supporting the development of applications and the deployment of these applications for specific business users. At least in initial phases this may discourage the app developer community, however.

FIspace 11.11.2015


The platform operator needs to choose whether or not to charge both sides of the business collaboration market. Plausibly the business user-sellers will be charged, possibly also the buyers.

A range of other revenue streams are also foreseeable, some of which will appear as costs for the plat-form operator. In some scenarios it is possible that the platform developer is not the same as the platform operator. While the platform developer is the partner that develops the software, the operator (used syn-onymously for platform provider) is the partner that brands and markets the platform and provides it on the market. In this case the developer could charge the platform operator including also service fees from the implementation. A platform host would also charge the operator for hosting the platform. Consultants and systems integrators (Business process engineers in the current terminology used in the project) could generate professional service fees for deploying applications at the user side. Financial service providers could generate revenue by charging a fee for clearing payment transactions. Providers of components such a GEs could also generate revenues from the platform.

It could also be noted that the FInest analysis as well as the SAF analyses implies that information and data will be very valuable in many applications, and could be used as a sort of currency in FIspace eco-system. This topic needs further analysis though.

FIspace needs to identify the key activities that will deliver its value proposition. A range of such activi-ties have been identified in the parent projects, including platform management, platform operations, hosting, service provisioning, marketing, continuous improvement, design and develop, consultancy, maintenance, promotion and networking.

Resources are necessary to create value for the customer. In parent projects these resources range from the platform technology, servicer, cloud, GEs, IPRs, applications, trust, personnel, etc. FIspace (the platform operators) will also need to provide a set of initial apps for two reasons (1) to stimulate early usage from business users and (2) to showcase how apps can be developed. At the same time, as men-tioned, FIspace third-party app developers will have to be provided with a number of incentives to develop apps, including SDKs, training, testing services and other support possibly complemented with monetary incentives in the early phase.

The FIspace platform operator should identify key partners and establish business relationships and alliances with other partners in the ecosystem in order to be able to deliver its value proposition to its customers. If we in FIspace consider the platform operator at core and business users and app develop-ers as customers, the remaining partners can then be considered as partners important for (the) FIspace (operator) to build a sustainable ecosystem. These roles (overlapping with Key activities above) taken up by these partners can in some case also be taken up by for instance (and eventually temporarily by) the platform operator. This entity then controls some of the key resource. Key partners to include in such an analysis are: hosting services provider, software developers, integrators and consultants (business pro-cess engineers), machine and material suppliers that provides business users (e.g. farmers) with equip-ment, maintenance and repair services and supplies. Certainly key partners cannot strictly be differentiat-ed from customer segments because of their equally valuable roles in some usage scenarios. However, this analysis should not essentially deviate from the thinking in the parent projects where this separation was introduced. Thus, some key partners and their respective roles are:

financial service providers: allow payments to be made;

industry associations: can crucially influence the adoption of FIspace, including standardisation and certification bodies;

governments / authorities: set rules and policies that could support the uptake of FIspace;

research institutes: can provide scientific knowledge that could improve performance of many ap-plications (flower decay, spraying, to name a few) and end-consumers.

In terms of cost structure, FIspace describes the most important monetary consequences while operat-ing under different business models. The cost structure of FIspace could (as analysed in the FInest pro-ject) in principle be divided into development, operating and marketing costs. A business model analysis should also consider the cost structure of other partners in the FIspace business ecosystem. In particular there will be costs for business users to hook up to and use the platform, to deploy applications along with possible complementary investments (e.g. sensors) and for app developers to develop applications, put them in the FIspace Store and market them. FIspace needs to seek to minimise these costs. We envision analysing these kinds of cost further for a selection of the trials, in later phases of the project.

This analysis forms an initial stepping stone towards a FIspace business model. In addition to providing a thorough list of factors for each building block in the Business Model Canvas, it provides conclusions for the platform that this deliverable builds on and refines.

FIspace 11.11.2015


5.2.2 FIspace Generic Value Network

The value network is disentangled in three phases. (1) The service development phase describes the tasks necessary for product and service creation (here mainly: the development of the platform and apps). (2) The service delivery phase represents the product provision to the users. In the case of FIspace, the main part of the platform is situated in this phase. (3) This results in the service consumption phase, where the product or services are used in a certain way to fulfil tasks or conduct roles. This ser-vice consumption phase is separated into three refined layers (depicted in blue) including the logistics and production supply chain (Figure 29).

Figure 29: FIspace Generic Value Network

In a next stage different configurations of partners can be mapped to the roles. One possible generic sce-nario is outlined in Figure 30.

Service

development

phase

Service

delivery

phase

Service

consumption

phase

Logistics

Supply chain

Collaboration Engine

Develop/maintain Apps

Develop/maintain

Baseline Apps

Develop/maintain

DSA/EUA

Develop GEs

App distribution in

the FIspace Store

Derive

Decide

Do

Provide Expert

Knowledge

App instantiation

Develop/maintain

FIspace Store

Custom Results

(Advice/Inform)

Develop/maintain

platform

components

Storing Transporting

Processing /

Assembling /

Packaging

'Producing' WholesalingSupplying Retailing

Store/manage

FIspace data

(access rules)

De

tect/D

ata

inpu

t

Business &

Legacy integration

Logging/Data

entering

IoT integration/

SensingExternal Data

provision

Tool-Kit for App

Instantiation/

customization

SDK for FIspace

App development

Profile creation

Profile/account

management

Data Access

Management

Platform hosting

Task%

Stage%Sub,Stage%

Store/manage

data

FIspace 11.11.2015


Figure 30: Main partners in the value network mapped to their roles

The role ‘platform’ is deliberately kept broad here, not denoting it as platform provid-er/operator/manager/developer. This is because multiple scenarios can be foreseen. In principle it is pos-sible that an integrated provider takes on the roles of developing, maintaining and operating (and even hosting) the platform, while these roles can also be separated. Multiple instances of the platform could also be foreseen (see the next chapter). One or several of the project partners could take up the further development of the platform or players from outside the FIspace consortium could take this role up These are key decisions, which will in turn influence the viability of different value network and business model set-ups, and will depend on decisions about IPRs and their terms and conditions that are set by the cur-rent partners.

In addition key partners (or suppliers) to the platform provider will be the hosting provider and the pro-vider of Generic Enablers. In principle the platform provider can integrate also the hosting role.

App developers/providers develop apps for the end-users (having the possibility to use other apps for this). They will be using the platform not only for developing apps but also publishing them, find other relevant apps for mash-ups and integration, provide (and possibly trade) software patterns for interacting with the platform and will have the possibility to capture monetary returns from the processes. The attrac-tiveness will depend on many factors such as: the availability and ease to integrate with other apps and support for app development in general, size of the market of business users, the possibility to capture value from business users’ usage of apps (revenue), cost of being on the platform (FIspace Store) of SDKs, to mention a few. Clearly the availability of initial (baseline) ‘seed’ apps will be key both for value proposition to app developers and to the value proposition to the business users. Terms and conditions for providing and for the reusing apps need to be settled.

Domain experts help the app developer with an understanding of the market and deliver content for the apps. The exchange of knowledge should be compensated somehow (e.g. revenue sharing) once an app

Service

development

phase

Service

delivery

phase

Service

consumption

phase

Logistics

Supply chain

Collaboration Engine

Develop/maintain Apps

Develop/maintain

Baseline Apps

Develop/maintain

DSA/EUA

Develop GEs

App distribution in

the FIspace Store

Derive

Decide

Do

Provide Expert

Knowledge

App instantiation

Develop/maintain

FIspace Store

Custom Results

(Advice/Inform)

Develop/maintain

platform

components

Storing Transporting

Processing /

Assembling /

Packaging

'Producing' WholesalingSupplying Retailing

Store/manage

FIspace data

(access rules)

De

tect/D

ata

in

pu

t

Business &

Legacy integration

Logging/Data

entering

IoT integration/

SensingExternal Data

provision

Tool-Kit for App

Instantiation/

customization

SDK for FIspace

App development

Profile creation

Profile/account

management

Data Access

Management

Platform hosting

Task%

Stage%Sub,Stage%

Store/manage

data

Platform

App developer Domain

Expert

Business Process

Engineers

App

GE

developer

Hosting

provider

Business

user

FIspace 11.11.2015


creates revenue. Domain Experts can either be independent parties or the user of the apps themselves (e.g. a farmer that has particular knowledge of his/her farm and data in the FMS and cooperates with an individual app developer).

The business users are those who use the platform (and an app) for their specific needs in their busi-ness operations. They are asked for their data input e.g. in the form of business and legacy integration. Their specific case demands and how they make use of the platform and the apps can be pre-defined as currently done in the trial set-up and objective.

The business process engineers customise and extend FIspace and its apps to the needs of end-users at an individual or organizational level. Depending on the usage situation these may be part of business users organisation, specialised consultancy, or even part of the service that the platform provides.

In conclusion, the value network of the FIspace platform indicates that the current design provides a meaningful division of roles. The current version of the platform can roughly be placed in the service de-livery phase as the intermediate of the two-sided market: app developers (in the service development phase) and the users (in the service consumption phase). Due to its wide functionality and possibility of usage, the platform’s roles are not limited to service delivery but includes the other layers as well. Having said that it is one single partner that can take up the all roles currently being taken by the platform. Plat-form development could be separated from the operations of the platform for instance. Such value net-work design choices are in turn dependent on who will take up these roles.

The app developer’s roles are stable and straightforward in the value network. In the basics, developers use parts of the platform to develop applications and distribute them via the FIspace Store. Additional roles are optional and appear only in some scenarios. Due to the neutral character of the platform on one hand, and the very specific business requirements of diverse sectors on the other, app developers might need support from domain experts to build useful and marketable applications. App developers are de-pendent on the data that is generated by the business users. App developers can be independent or col-laborate with a company or business user for whom they develop customised apps. Hence, they might be subsidised directly by the business users. Apart from that, the platform can help stimulating the app de-velopment by building the basic infrastructure, support the access to data, provide support (SDKs) or other incentives for the app developers, such as minimizing entry barriers for developers.

It is mainly at the lower layers of the value network where the implementation of the roles by the partners varies per usage situation. This stems naturally from the different options that the platform envisions to support. The value of the platform for the business users can and will be measured by the means of dif-ferent parameters. This task will be one of the main focuses of the future work.

Though the value network depicts the current status, roles—and the partners that conduct the roles—as well as their terms and conditions might change according to the exploitation of the platform after the FI-PPP Phase 2 period.

5.2.3 Basic Business Model Scenarios

Eight scenarios for the platform’s business model appear to be feasible at the current status of the pro-ject. Since they are still dependent on the development of the platform, configurations of parameters are partly based on assumptions and interpretations. In short, these scenarios are:

The first scenario is that an ICT or software company from within the project takes up the role as the platform provider.

Similar is the scenario that an ICT or software company from outside the project steps into the position of the platform provider.

There is a possibility of a new start-up, an organization that has no other businesses then to pro-vide the platform.

As another solution, it could be possible that no internal or external party applies to become a FIspace platform provider after the end of the FIspace project. In that case, the project partners could opt for the scenario in which they create a consortium of project partners to keep the platform operational for the time being, and possibly develop its functionality further).

It is possible that a group of important business players in relevant industries (e.g. logistics, argi-food, assembling) sees the benefit of a centrally provided FIspace platform, but none of these players is willing to become a platform provider themselves, e.g. because they lack the finances, or it would be too far away from their core businesses. In that case they could collaborate and to-gether found a joint venture of industry players to be a platform provider.

FIspace 11.11.2015


Another scenario is that of a non-profit organization or university interested in taking up the role of platform provider.

The platform’s functionality can be taken up by a public authority, i.e. a European, national, fed-eral or regional governmental organization. An example is the project partner OPEKEPE, the Greek National Organisation of Agricultural Development and Funding, Control, Orientation and Guarantees for Community Aids.

Another possibility is that the platform is taken up by one company in a specific sector or do-main to serve just this sector or domain.

It is also a possibility that multiple instances of FIspace (eventually developing simultaneously, eventu-ally drifting apart) will run in the future. These multiple instances will mix would then mix features of the above (and is therefore not listed as separate scenario in the table below).

These scenarios can materialise at the moment of commercialization of the platform. It implies the mate-rialization of some factors that positions the platform in the market. Table 5 depicts an overview of the most relevant factors upon which the business model scenarios (potentially) differentiate. Additionally to these, several business model parameters were identified that the platform provider needs to decide up-on, independent of which scenario will be realised. These parameters influence the choice for a particular business model and strategy of the platform. Conversely, parameters are influenced by the choice of the platform business model and strategy.

FIspace 11.11.2015


Table 5: Comparison of business model scenarios

1. ICT or SW company from within FIspace

2. ICT or SW company from outside

3. New startup

4. Consortium of project partners

5. Joint ven-ture of indus-try players

6. Non-profit organization or university

7. Public au-thority

8. Company in a specific sec-tor or domain

Open or proprietary TBD TBD TBD Open Likely open Open Open TBD

European owner Yes TBD TBD Yes TBD TBD Likely yes TBD

Hosting Likely self Likely self Likely self Self Third party Likely third party

Likely third party

Likely third party

Goal of platform Profit or cross-subsidisation

Profit or cross-subsidisation

Profit

Trajectory towards one of the other sce-narios

Functionality Functionality Functionality Profit or cross-subsidisation

Domain-specialization No No No No Yes Likely No Yes Yes

Possibility to bundle products

Yes Yes No No Unlikely No Unlikely Maybe Yes

Apps published by the platform provider

Yes Likely Likely Yes Possible Possible Possible Likely

Attractiveness for developers

High High

Medium (rises when start-up shows poten-tial)

Low High Medium Medium Low

Attractiveness for business users

High High

Medium (rises when start-up shows poten-tial)

Low High Medium High Medium (de-pending on authority)

Platform as intermedi-ate of Two-sided mar-kets

Yes Yes Yes Yes No Yes No Likely No

Adoption decisions Optional Optional Optional Optional Collective Optional Authority Authority

FIspace 11.11.2015


5.3 Potential Constraints

FIspace was analysing of what will be the main constraints to develop and deploy FIspace at a European level and in other countries and companies outside Europe.

Fispace is essentially a communication platform that links partners and their own ‘ecosystems’ to each other and to 3rd parties who provide or process data.

FIspace therefore performs the following duties;

Setting up any requested link between partners and data providers based upon the protocols re-quired, the envisaged volume and the regularity of the needed data.

Proving the link and testing the data transmission to sign off by the partner.

Managing the communication flow.

Resolving issues, ensuring data security during the period it moves it between partners and effi-cacy i.e. data arrives in the same format it was sent.

It engages with partners at two levels;

Through an initial agreement with the partner stating the ownership of liability for the use of the data, the resolution process for disputes, the terms of use of the platform etc.

Through agreements per communication message that state the parties sending and receiving the data, the regularity of the data, the size of the data packets and other base information.

The underpinning principle of the FIspace platform is that it provides enabling technology and is not inter-ested in the nature of the data being moved. It stores no data apart from the basic essentials to enable the data movement and certain details about the partners sending and receiving the information. This last element is to allow better problem resolution.

Therefore, the only direct constraints on the FIspace platform to allow it to perform its function are data privacy laws and the usage of the stored data.

The impact of indirect constraints however needs to be considered when analysing the barriers to suc-cessful exploitation.

5.3.1 The challenge of financial liability for failure of the platform

The major concern however is around the issue of data ownership and corrupt data files preventing the proper working of the platform. As FIspace is intended to be a business enabling technology then many organisations will be relying upon it to function correctly to allow them to exploit their commercial opportu-nities. Should the platform fail for whatever reason then they could incur financial loss which they would look to mitigate somehow. The normal method to do this would be through imposing penalties on the platform for not meeting an established agreement. If FIspace is successful there could be many of these types of agreements in place and therefore any failure could be very expensive. FIspace would look to offset this liability to the partner / app developer who may have created the failure through poorly written code or data corruption. However, the same financial liability would now be placed on this organisation / individual and therefore this could also be very expensive, if not ruinous, to them. This issue could pre-vent the full exploitation of the platform as no-one wishes to have to sign a ‘blank cheque’ for a single failure that disrupts the entire platform. In actual fact, this issue becomes even more challenging as 3rd party organisations who are supplying data to the partner via FIspace may be the cause of the issue but they would have no liability apart from what they have agreed with the partner. So the failure may not be the partner’s problem but they then become liable.

To resolve this challenge, the FIspace platform needs to continue to work even if there are processing issues with certain files. The technical challenge is to guarantee that there is 100% up time even if certain processes do not complete correctly. It is also to ensure that the failure in one partner’s process does not have a consequential impact on all other partners.

The limitation of liability must also be restricted to the amount of money that the partner puts into the FIspace platform originally unless there are legal exceptions.

The financial liability issue must not be a barrier to uptake of the FIspace platform.

FIspace 11.11.2015


5.3.2 The challenge of jurisdiction

FIspace is designed to be neutral but it has to operate within a legal framework. This would normally be the laws operating in the country where the FIspace is incorporated either as a Foundation or any other legal organisation. As FIspace will cross borders with regards to data communication then the laws that can only be applied will be the ones in the incorporated country. This would need to be clearly stated in the agreements with the partners. If the laws are different in the countries they wish to operate in then it would become their responsibility to ensure they were complied with.

This does require the partner to understand the nature of the laws in operation in the countries using their application. This is not a barrier as such to FIspace but does place constraints and potentially barriers to the partners wishing to exploit the platform.

5.3.3 The challenge of flexibility vs. legal constraints

FIspace needs to be able to balance legal obligations with the freedom of app developers and organisa-tions to create new business models and opportunities.

It is imperative that the minimum amount of legal constraints needs to be placed on the partners using the platform. Rules constrain creativity and a ‘light touch approach’ towards the use of the platform needs to be maintained to encourage greater acceptance and exploitation. There will be an ongoing challenge to FIspace to ensure that legal considerations do not become a barrier to usage.

5.3.4 Conclusion about Potential Constraints

Creating a neutral platform for businesses to collaborate across borders is somewhat more challenging than normal cloud based solutions, in that, commercial exploitation requires risks to be taken, invest-ments to be made and commitments of time and energy to be undertaken by the partner community. The FIspace platform enables new opportunities for these partners but at the same time they are placing con-siderable reliance back on the platform to perform effectively. Individuals using cloud solutions may not lose out financially if their platform is unavailable but commercial organisations will.

FIspace therefore needs to balance the constraints of having to work within a legal framework for its own protection and at the same time provide flexibility to the partner community to create their new business opportunities. The power of harmonising rules over data security and usage across the participating coun-tries can therefore also not be underestimated.

Therefore the exploitation of FIspace as an opportunity for new business models is a balance between the constraint of the legal framework it needs to work in and the flexibility required by the partners. This needs to be maintained throughout the evolution of the platform. It is crucial that this balance is identified and enshrined somehow in the principles of FIspace so that one element does not compromise the other and ultimately kills the opportunities provided by the platform.

FIspace 11.11.2015


5.4 The FIspace Foundation – Next Steps towards Commercialisation

After the end of the FIspace project, it will shift to a more commercial mode. The FIspace project will re-lease an alpha-version (a pre-commercial version) of the software, which means that a considerable in-vestment would be needed to bring it to a beta-release, which will be a commercial version of the plat-form, but in a juvenile stage. From this beta-release the platform needs to be further commercially devel-oped.

One could imagine that several companies or organisations inside or outside the current consortium would like to pick up commercialisation of the FIspace platform. A FIspace platform could be owned and run by a strong company in an industry (e.g. a major retail company in food, or a logistic provider to or-ganise data exchange with its sub-contractors, or a public service like a paying agency in the Common Agricultural Policy that has to organise data exchange with 100.000+ farmers).

But for the FIspace platform to succeed (and stay close to its rationale of making data of business part-ners more open) it is more likely to succeed in the hands of a “neutral” party. Another aspect of the com-mercialisation is that end-users (like food or logistic companies and their farmers) do not want to depend for an important part of their business transactions on one commercial offer that does not face competi-tion. A monopolistic solution would lead to a vendor lock-in problem with potentially high costs for the end-users.

Therefore it has been decided that the FIspace project will move its know-how, standards, code and plat-form into a Foundation that guards its open source character. The Foundation will license the use of its code to commercial companies or others that want to exploit a FIspace instance as platform operator, and will overview the interoperability between those instances. Even if only one company would exploit FIspace in the beginning, this construction guarantees potential competition in case the end-users are depending on FIspace for their business, but not satisfied with the service or price setting by a platform operator.

Figure 31 shows how FIspace could be further commercialised, based on the foundation. The current alpha-release will serve as the FIspace Lab that can be used by the FIWARE accelerator projects. How-ever it could be extended in the future as an experimental environment for development of new apps and services. Several commercial instances of the platform can be established by companies, facilitating an ecosystems of end users and solution providers in a specific domain or region. Figure 31 only provides a few possible directions; there are many other opportunities to be filled in. The next sections will elaborate this development in more detail.

Figure 31: Commercial development of the FIspace platform based on a foundation.

FIspace 11.11.2015


The FIspace Foundation was officially created in August 2015. The general objective of the FIspace Foundation was formulated as follows: The Foundation aims at supporting and increasing the use of software and knowledge of the FISPACE project, as handed over to the Foundation by the original devel-opers in the FIspace project. At the same time, the results and work of the foundation will be handled in accordance to the FIspace consortium agreement.

The board of the Foundation was formed by persons with a different background. It includes people who are employed by FIspace platform operators, app developers, end users and research institutes. They govern the FIspace Foundation and are aiming at activities of the Foundation to ensure that the FIspace platform is:

Forever neutral (and not dominated by any single organisation)

Structured and standardised globally

Transparent, trustworthy and secure

Available to create new ecosystems

Available to all, inside and outside the European Union.

Continually growing and evolving to keep up with technological developments and user needs, with a minimum of development patterns that might create restrictions for future exploitation

Affordable and robust. (High costs for technical services will negate the benefits to many SME’s. Low costs will only happen if there is competition in all development and technical aspects.)

Commercially attractive for companies that exploit FIspace as a service to end-users, that must earn a rate of return

A situation with several FIspace platform instances does not have to be problematic for interoperability. Like there are several web-browsers (Chrome, Internet Explorer, Safari, etc.) and several e-mail pro-grams, there could be several FIspace platforms. That requires a standardisation of the FIspace open protocols, comparable to the W3C-consortium that governs the world wide web protocols. The FIspace Foundation will organise a procedure for dispute settlement in case different platforms (instances) are not interoperable.

Therefore, the Foundation is comparable to the Linux Foundation in the sense that it runs the FIspace as an open-software community with limited budgets and leaves the commercialisation of FIspace instances to commercial companies. This implies among others that the Foundation:

Manages the components and standards in FIspace communication

Grants the FIspace trademark/product (FIspace certification)

Markets the principles of FIspace to establish new ecosystems and get new parties on board

Resolves disputes between parties using FIspace standards and components

Agrees on the expansion of the FIspace functionalities and includes new standards and compo-nents in new releases

In the first year of its existence the Foundation will focus on the following activities:

Secure the handing over of all material from the FIspace project to the Foundation by working with the FIspace project management group (PMG) and the technology partners during the runtime of the FIspace project and in its finalisation/final reporting phase. Drawing up contracts, taking over the website and software as well as asking a company to curate that material on a website.

Ensure the protection of IPR of the software being managed by the FIspace Foundation.

Collaboration with those FIspace project partners (beneficiaries) that are maintaining the public FIspace platform (i.e. experimentation environment) that is kept online also after M30 of FIspace to offer FIWARE phase 3 projects an initial environment to learn about the features, usage and development based upon FIspace.

Find companies or other organisations (e.g. paying agencies or others) who want to create an in-stance of FIspace for their business and end-users. That is finding opportunities and drawing up a contract on the use of the software.

Possibly join new (EU) projects as a partner to further develop FIspace.

Organise an event for next winter (early 2016) to bring the FIspace community together for ex-changing experiences, discuss further innovations etc.

The FIspace Foundation builds its sustainability plans on the expectation that the generic enablers used in FIspace will be available in the future. The FIspace Foundation is open for collaboration with the FI-

FIspace 11.11.2015


WARE Foundation, to foster the sustainability and innovation of the FIWARE generic enablers as well as FIspace.

Another crucial point is the relationship between FIspace and some Phase 3 accelerators. Supporting activities are strongly connected to and relying on the Phase 3 developer community. As a consequence Phase 3 support also plays an important role in raising awareness of FIspace B2B platform between de-velopers and other stakeholders (SME incubators, SME associations, venture capitalist, infrastructure owners, intermediaries in general constitute etc.).

The aim is to maximise the number of engaged developers, reaching them mainly through FIWARE ac-celerator programs. The final and stable version of FIspace will attract more participants and towards the end of the FIWARE program broader community activity is expected. Through the FIspace Foundation, community building becomes more open thus it will reach wider target groups.

FIspace 11.11.2015


6 Policy Recommendations

FIspace analysed the present situation, barriers and opportunities in the present regulatory scene in Eu-rope, plus a formulation of proposals towards developments in policy and private sector regulations that could exploit FIWARE technologies for better realizing and integrating the needs of industry on one side and the expectations of regulatory bodies (in policy and private sector initiatives) on the other side.

The recommendations listed in the next sections are grouped in relation to private and public stakehold-ers in the agri-food and logistics space.

6.1 Recommendations for Private Stakeholders

This section discusses what proposals could be made for policy to change, written from the perspective and for the advantage of private stakeholders in the agri-food and logistics space.

As noted in many of the FIspace deliverables, the agriculture, food and logistics sectors have certain unique characteristics that make them substantively different from other industrial sectors (such as the automotive, plastics or electronics sectors). The first of these is that food and agriculture are highly regu-lated sectors (logistics is somewhat less so) and thus government policy plays a more substantive role than in other sectors in defining the playing field for stakeholders in the market, and consequently the opportunities for an ICT platform such as FIspace. In the European context, the most important law is the European Food law which operates together with a multiplicity of regulations covering health and con-sumer product quality. The most recent of these, for example, is the law concerning allergies and labelling which came into force in December 2014. The second characteristic is the diversity of stakeholders across the supply chain. In spite of decades of consolidation, there is a very large number of different types of actors, and when it comes to farmers and retailers, a very great number of different business entities. These two characteristics – the overarching presence of regulation, and the infinite variety and number of actors – make all policy proposals problematic because inevitably it is hard to avoid damaging the interests of one group or another. For example, from a regulatory perspective, it would be ideal to have total transparency of the food chain, with constant visibility (“legibility”) so as to either avoid any food crises or at least allow very rapid response. From a food producer’s perspective (as things stand at the moment before FIspace) such transparency would be potentially very damaging for business or at least would imply an immense cost of data capture.

In this light, the following suggestions are proposed in full awareness that any single proposal will affect the interests and preferences of one type of stakeholder against another.

Impose electronic record keeping. Currently the law demands merely one-up, one-down recording keeping without specifying in what format such records need to be kept. This has meant that naturally most record keeping is in the form of paper invoices and receipts which mean that in the case of food crises data collection is painful and laborious.

FIspace Perspective: This would make the use of a platform such as FIspace extremely attrac-tive especially as apps could be offered to facilitate such record keeping and integrate this other offering

Problems: Careful thought needs to be given to the scope of electronic record keeping. One ex-ample has been the controversy surrounding the obligation to sell olive oil in a pre-packaged form in restaurants. This was presented as an endeavour to guarantee olive oil quality in restaurants under the supposed fear of adulteration by restaurateurs. In fact this caused a substantial back-lash from restaurants due to the additional cost and inconvenience, plus it would disadvantage significantly small scale oil producers who sold to their local restaurants/taverns.

Impose standardized data exchange formats. In order for a real ecosystem to grow around data services, there must be consistency in data exchange syntax and semantics. This is a problem in all areas ranging from agricultural machinery to farmer-retailer information sharing. As documented in Deliverable D500.4, the problem is not a lack of standards but rather the lack of clear imposition of an appropriate subset. Such an initiative would be beneficial especially for smaller enterprises who could then use of the shelf systems and know that they would inter-operate with a number of different other systems.

FIspace Perspective: Because FIspace has been designed to be a platform that is agnostic as to the data formats travelling through, there is still the potential for considerable failure of inter-operability. Such a regulatory initiative would benefit a large proportion of stakeholders in the agri-food system (apart perhaps from large incumbents who have invested in bespoke systems).

FIspace 11.11.2015


Problems: The imposition of standards of any sort by governments has always been extremely slow and often problematic. However, current efforts in standardization bodies (ranging from GS1 to ISO and W3C) are not making adequate progress given the rapidity of the changes occurring both in technology and the business environment. Thus some kind of initiative at a regulatory level is called for.

Provide clarity on data ownership and sharing. As noted above (Section 3.1), there are existing laws or data privacy and ownership. However, scenarios where multiple stakeholders are involved in providing services will create conflicting views as to data ownership and potential secondary usage. There are concerted efforts by some large companies (Monsanto, John Deere) to “own” the data stack and we will rapidly find ourselves in a situation where one or two companies control very large amounts of agricultural, food and logistics data. First mover advantage and the network effect will create monopolies very rapidly if appropriate regulation is not put into effect.

FIspace perspective: Although as noted above (Section 3.3), there is the danger that FIspace becomes and apparently monopolistic platform, it will be important to emphasize the FIspace Foundation and its overall ambitions. FIspace must be an open platform which neither locks user in nor creates impediments for new services and service providers. In such a context, a regulatory initiative on data ownership and sharing will be beneficial.

Problems: The most likely resistance here will come from large incumbents who believe they have a chance to have sufficient market share so as to not wish to have clarity on data ownership.

Create appropriate regulations for cross-border service provision. There is a growing sector in cross border services (typically financial or insurance at present). Appropriate regulatory support for cross-border services will make it easier for services to be provided between countries and facilitate the development of a pan-European agri-food and logistics services market. This concerns not just the actual delivery of physical services (e.g. transport) but also meta-services (e.g. data manage-ment, billing services, advisory services etc.). This is necessary not just for economic development but also because it makes the provision of services on a platform such as FIspace more economical, providing a larger market etc.

FIspace perspective: For a platform such as FIspace to succeed it needs to be able to operate across many different borders and jurisdictions. Unless there is greater regulatory clarity and cor-responding legal indemnity, many stakeholders will be loathe crossing borders for fear of unin-tended or unforeseen consequences.

Problems: The opening up of services across Europe is still an ongoing process with many local restrictions and cultural differences making this a challenging area. However, as agriculture, food and logistics form part of the backbone of European integration, this is an area that policy and regulation must not forget.

6.2 Recommendations for Public Stakeholders

Based on various European policy initiatives the FIWARE technology opens up important opportunities especially for the food sector which is still far behind others sectors in the utilization of information tech-nology. This is especially true with regard to the exchange of information between enterprises and with consumers.

A critical issue concerns the difficulty of organizing closed production chains which would allow internal communication agreements but the need for open network organizations which could manage the high variability in the production of agricultural products. As a consequence, sourcing of products might have to be based on changing suppliers, i.e. the sector needed a sector wide infrastructure of comparable technology which reaches beyond country borders.

The FIWARE technology provides this opportunity but needed policy support to reach the desired impact. Some specific issues are discussed in the following:

1. Tracking and tracing

Opportunity: With the FIWARE technology allows to easily link enterprises along the chain and their ERP system environments for communication and data exchange without storing chain rela-tionships (an issue of competitiveness) at a central place for access by chain participants. Track-ing and tracing is facilitated by utilizing FIWARE apps that allow to link the different systems with apps that provide functionalities for exchange and for interfacing with individual ERP systems.

FIspace 11.11.2015


Problem: A sensible tracking and tracing system would require that all members of the chain or network are participating in the exchange. Investment by any individual company would make it tracking/tracing ready but would not solve the communication requirements along the chain. Fur-thermore, communication along the chain would be limited by the stage with the lowest level of technology.

Policy challenge: The food chains and networks need facilitators that support joint investment action by stakeholders. It might need support through regulatory policy initiatives which require appropriate data communication along the chain starting with a detailed tracking and tracing op-portunity which covers all stakeholders involved in getting agricultural products to retail and con-sumers. These initiatives should be linked to requirements on the speed and data content in case of quality or food safety deficiencies which would require the utilization of appropriate digital tech-nology along the chain.

2. Data on food quality and safety for serving consumers (transparency)

Opportunity: Transparency within food chains and towards consumers regarding food quality and food safety is a general requirement in discussions on the sustainability of the food sector. The FIWARE technology with its ability to easily link data processing systems of various stakeholders provides the opportunity for reaching the goal with limited investments if compared with previous technologies.

Problem: If not forced by law, each company will only collect data for exchange with its trading partners if it is assured that the data are being used by recipients as agreed upon, that it benefits from data communication, and that its data collection efforts are being appreciated by recipients. These requirements are especially relevant for agriculture as individual farms usually represent the weakest stage in the chain. It is therefore widespread that farmers refuse to participate in data exchange.

Policy challenge: One of the issues that need policy attention are the organization of data mar-kets where data trade could take place. Any such markets need some basic regulations. If market participants are not engaged in getting such markets with appropriate support of weaker partici-pants in place, policy would have to step in. Data markets would build on clear regulations regard-ing data trade, clear agreements on data use and on appropriate pricing systems. FIWARE de-velopments could provide appropriate tools for realizing the technological base which needs to be linked to regulatory policy initiatives.

3. Data reliability

Opportunity: The FIWARE technology facilitates data communication along the chain and sup-ports transparency in food safety, food quality, and delivery reliability.

Problem: The data communication along the chain runs parallel to the exchange of products. While there are public food safety controls, there are no similar controls regarding the reliability of data. However, they determine food trade and the trust of consumers in the quality and safety of food. Distrust of consumers in provided information may damage markets.

Policy challenge: Policy needs to take action and to provide data reliability controls similarly to food safety controls. A key requirement is the neutrality of data control which is independent of market participants.

4. Data security

Opportunity: The FIWARE technology facilitates exchange of data between enterprises within a chain but also between countries on a global scale.

Problem: Assurance of data security in the absence of global security standards and controls.

Policy challenge: The security of data needs to be protected by policy regulations within a coun-try but also on a global scale. Furthermore, policy must provide data security controls within a country but also on a global scale. Data security guarantees based on appropriate controls are a prerequisite for companies providing their data for use along the chain which might reach beyond country borders.

FIspace 11.11.2015


7 Innovations

The overarching innovation of the FIspace project is the FIspace platform, which is an extensible SaaS cloud offering that can be extended by means of (1) adding functionality through Apps, (2) defining col-laborative processes, (3) integrating data sources of users. Beyond the concrete technical realization of the FIspace platform, which required several technology innovations, the concept of the FIspace platform also triggered the incubation of innovations on top of such platform concept. As part of the FIspace pro-ject, many individual innovations have been made. Many of those were essential to delivering the FIspace platform, others were triggered by the FIspace platform itself. This section describes these individual in-novations of the FIspace project as reported by the project members.

The innovations are structured along four main clusters:

App (see section 7.1): represent innovative new kinds of apps and services that are made possible by the FIspace concept;

Platform (see section 7.2): cover innovations related to specific components and features of the FIspace platform itself;

Infrastructure (see section 7.3): relate to novel ways of collecting and integrating data sources that may be integrated with the FIspace platform.

Process (see section 7.4): relate to innovations in business processes that are possible through the FIspace platform and app, or that support the FIspace concept

The following sections provide a summary of the innovations. A more detailed description of these inno-vations can be found in section 7.5, as well as on the FIspace website at (www.fispace.eu).

7.1 App Innovations

Name Summary

A1

Improved Shopping Experience App

The Apps provides clients with a set of functionalities in just one app which will make their shopping experience much easier than before. All these functionalities have been developed in Android and iOS in order to obtain a better market acceptance. Consum-ers can manage their shopping lists by adding real products from the supermarket. Moreover, the app even suggests different recipes based on consumer preferences and health information. Consumers can access tailored product information at the su-permarket via the mobile device by means of augmented reality. Furthermore, custom-ers will receive real time information from the supermarket about the best offers and alerts. What is more, they can send feedback about the products to the supermarket.

A2

Fresh Food Transparency Apps

The transparency Apps for fresh food, in particular meat, have been developed based on the new EPCIS standard that can handle irrevocable events, e.g. a slaughtered cow can never become alive again or even one single piece as it was in the beginning. The Apps are based on a system that consists of one or more EPCIS repositories that con-tain all events of a meat item starting at the farm, and subsequently passing the slaugh-terhouse, meat processors, distributors and or cold store to arrive finally in the super-market.

A3

Consumer Goods Im-port/Export Apps

This innovation is concerned with planning and execution of logistics activities in the consumer goods sector ensuring effective planning of related activities resulting in im-proved coordination, loss minimization, efficient use of resources and high customer satisfaction level. Effective planning and timely monitoring of the transportation process is crucial since unexpected delays might lead to problems and losses in several stages starting from the production activity till the delivery of finished goods to the customers. It improves collaboration between different stakeholders during the transport demand description process and it makes information available to users till the end of the exe-cution of the shipment.


FIspace 11.11.2015


Name Summary

A4

Cargo-SwApp

In the short-sea container market, the carriers face problems as low visibility and pre-dictability of the transport demand, low customer loyalty and a high number of late transport booking cancellations, mostly due to lack of collaboration or access to infor-

mation. This results in short time windows to find new cargo, extra work on re‐planning

and sub‐optimal use of transport capacity. It is common that 30‐40% of cargo is can-celled close to the cut-off time. The CargoSwApp was developed to cope with these late cancelations and enable carriers to quickly react and find replacement. CargoS-wApp also offers the possibility to assess each booking, and enable the carrier to antic-ipate cancellations, thus using overbooking in a more effective manner. By extending the scope of the CargoSwApp, functionalities for shippers have also been added: the possibility to search the marketplace via CargoSwApp and benchmark service offers at shipment level. CargoSwApp allows for immediate information exchange between shipper and carrier.

A5

Botanic Trad-ing Infor-mation App

The prototype Botanic App offers valuable trading information to professional growers and traders in flowers and plants. It offers anytime and anywhere access to the correct taxonomic product descriptions, trading codes (VBN codes) and availability throughout the year. Reduction of errors in communication and ordering is expected, which en-hances the efficiency in the supply chain.

A6

RISKMAN App

RISKMAN significantly differs from other warning systems. RISKMAN offers a collec-tion of structured (contracted laboratories, public authorities (i.e. EFSA)) and unstruc-tured information items (i.e. social media networks) in order to provide a collection of potential information on risks in the distribution of fruits and vegetables to the users of the app (i.e. risk man-agers of agri-food companies). It therefore represents a special and innovative type of news centre for critical information on food safety, which we consider as an early warning system.

A7

BizSLAM App

BizSLAM is a cloud-based software component that automatically manages multi-level SLAs by extending SLA management solutions from service-oriented computing. SLA management of transport and logistics services significantly differs from SLA manage-ment of cloud or web services due to the important role that frame SLAs play in con-tracting. A frame SLA is a general agreement that constitutes a long-term contract be-tween parties. The terms and conditions of the frame SLA become the governing terms and conditions for all specific SLAs established under such a frame SLA. Not consider-ing the relationships between frame SLAs, specific SLAs and QoS monitoring infor-mation may lead to partial conclusions and decisions, thereby resulting in avoidable penalties. BizSLAM delivers a multi-level run-time SLA management approach for transport services that takes into account those relationships.

A8

Bad Weather Warning App

Different fumigation products have optimal application conditions, drying time, absorp-tion rate and retention time. For that reason, sprayer operators seek a lot of information about the weather and the environment with of high accuracy (up to field level). To achieve this goal, the Workability Data App has design and develop an automated de-cision-making prediction module which shall help the farmers to decide the most suita-ble period for their spraying activities and notify them if the forecast prediction has changed. The App calculates the spraying conditions for a particular location based on the criteria specified by the farmer and the chosen dataset containing the weather pre-dictions (wind speed / direction, probability / type and intensity of rainfall, temperature, humidity, etc.). Once the spraying activity has been planned (using the scheduling app), this App module gathers the information in order to periodically check that the weather prediction updates don’t affect the scheduled activity workability. Depending on the preferred weather provider, the App can check the forecasts several times per hour. If the value changes significantly, for example not allowing for the execution of the spraying, this module will send a push notification to the farmer mobile terminal and other selected platforms, reporting him about this unforeseen event. It allows re-starting the cycle if the farmer deemed it appropriate

FIspace 11.11.2015


Name Summary

A9

Traffic Light App

The Traffic Light App allows supermarket customers to access important information about certain product attributes they might find useful. The app shows in a clear way whether the attribute associated to the product is in a dangerous level, a normal level or a good level based on rules previously de-fined. An administrator can create and later update these rules if necessary. The customer asks for information using the product id and sends the request to the server that searches for the product information and applies the rules. The information is then shown on the screen where each attrib-ute is coloured in green, yellow or red based on whether it is considered good, normal or dangerous, respectively. The innovation of this approach relies on the provision of rules in product information making the application configurable and adaptable to other conditions or food parameters.

A10

BOXMAN App

BOXMAN is a first App that reaches beyond enterprise borders and realizes a chain encompassing management of packaging (crates, boxes) across the whole food chain reaching from production agriculture until retail. All enterprises are involved in reporting the movement of crates (in and out) while the central box management company as-sures that demand of boxes by enterprises are met at all times and that empty boxes are cleaned upon being returned by retail companies. Despite the chain encompassing management application, each company runs its own web-based application which is linked to the box management group. The App provides transparency on the carriers of products which provides the basis for other applications such as tracking and tracing of products, the identification of origin, the monitoring of product quality, etc.

A11

Product In-formation (PIA) App

PIA is an application that reaches beyond enterprise borders and realizes a chain en-compassing exchange of information between stakeholders across the whole food supply chain, reaching from production agriculture to retail. This application provides a solution for many problems the food chains are presently experiencing. It provides transparency across the chain on product characteristics, product quality, characteris-tics of production processes (e.g. inputs in agricultural production), logistics, tracking and tracing needs, and more. It also provides the basis for monitoring product quality and deliveries along the chain. At retail, PIA provides the interface for applications that communicate information to consumers. Beyond its reach across the chain, its innova-tion is in the separation of the information exchange into a sequence of individual apps that are run by individual enterprises, i.e. it is not based on a central data management approach. This innovative decentralized data management approach, enabled by the FIspace platform, overcomes a core barrier for adoption of information exchange solu-tions by the food sector.

A12

Tailored In-formation for Consumers Apps (TIC)

This App complements the B2B PIA App by providing an end-user interaction and visi-bility to the supply chain. One important concern is the provisioning of accurate infor-mation to individual consumer´s needs. Two complementary Tailored Information for Consumers Apps address this concern. The TIC App’s main objective is to collect and store links of the different product information providers. This information can be made available to other Apps through the FIspace platform capabilities. The TaPIA App’s main objective is to provide to consumers static and dynamic information of a product according to a profile where each consumer can choose which product attributes he/she want to know. This mobile application is adapted to each profile and range of information needs of consumers.

FIspace 11.11.2015


7.2 Platform Innovations

Name Summary

P1

FIspace Stu-dio

FIspace Studio is the Software Development Kit (SDK) that provides tool-support for the development of FIspace Apps. The SDK eases the work of App developers during the implementation of the Apps, providing specific tools and hiding the complexity of the platform. Also the Business Process architects find the proper way to manage the business entities at FIspace platform. The SDK for FIspace consists of a collection of Eclipse plugins available to be installed and the FIspace Studio Tool (which is the bina-ry distribution of such plugins). Also, a set of libraries implemented in several pro-gramming languages provides the FIspace user with the appropriate tool to connect to the platform. FIspace Studio Tool is represented by an Eclipse Rich Client Application. The distribution provides the required user interface for all of the pre-installed FIspace SDK functionalities along with a customized approach of the Eclipse IDE reaching the specific needs of FIspace platform.

P2

Business Pro-cess Collabo-ration and Complex Events

In today’s competitive and dynamic landscape, business managers are continuously forced to effectively react to any event that has the potential to affect the expected course of their business processes. To cope with this requirement, companies are in-creasingly adopting business process engines alongside with event processing en-gines, to manage their business process and get real-time alerts once a situation re-quiring a course of action occurs. However, these two engines deal with different busi-ness logic and programming models and, as result, integration between the two is far from being easy. Business process engines are usually synchronous and the process encompasses sequential steps or tasks to be performed. Event processing engines are by nature asynchronous. Events can happen in any order and an action is taken in a reactive mode. The B2B component in FIspace, composed of a business collaboration module (BCM) and a (complex) event processing engine (EPM), offers a seamless integration between these two types of engines. The artefact-centric approach for busi-ness processes is reactive and asynchronous, and events are the ones responsible for the progress in the flow. Moreover, the programming model of the BCM supports the inclusion of events as a building block in the programming model making the integra-tion easy. While the event logic is done within the EPM, the output events can be guards and milestones in the BCM programming model.

P3

Ygg: Capabil-ity-driven Cross-Organizational Business Col-laboration

The core functionality of Ygg is to facilitate business to business collaboration. The main way Ygg supports this is via business processes. Characteristic of these business processes is that they exceed the boundaries of one business. All Ygg core compo-nents are involved in supporting those business processes. A business process in Ygg is implicit. This means you don't have to define or describe one explicitly. A process owner only has to define in Ygg that he is capable of providing a specific service. A different stakeholder then can in turn use this capability. This introduces the concept of capability. The benefit of using capabilities is that all capabilities providing similar ser-vices would look the same. That way a stakeholders would be able to switch from one service to another without making a lot of adjustments in his software. For this reason Ygg contains a registry with defined capability types.

P4

Composite Service Bus

The Composite Service Bus (CSB) is a middleware that enables integration of different FIspace service components and applications. CSB provides a set of integration inter-faces and qualities of service, required to support a wide spectrum of information ex-change scenarios, ranging from best effort notifications, to guaranteed delivery of transactional data. CSB has virtually unlimited scalability, both in the number of sup-ported end-points, and in the number of communication channels allowed by the Bus transport fabric. The scalability challenge, posed by the large number of data produc-ers, service providers and consumers in this cloud-based project, is addressed by Peer-to-Peer overlay technology. The CSB core is comprised of Bus Nodes, connected by a peer2peer structured overlay fabric. The CSB clients are the FIspace service components, using the Bus for integration and connectivity. This two-tier architecture allows us to build an enterprise-strength service bus, with extensive functionality set and assured delivery of transactional data.

FIspace 11.11.2015


7.3 Infrastructure Innovations

Name Summary

I1

Low Cost Wireless Sensor Network based on Open Hardware

To engage small-medium farmers into next generation agricultural processes, it is essen-tial to present them with products and services that have as low entry cost as possible. To this end, a simple, effective and low cost wireless sensor network deployment was need-ed so that farmers will benefit the most from what a platform such as FIspace has to offer. However it is often the case that sensor network equipment is really expensive and is only compatible with the vendors’ software management solution. This leads not only to ven-dor lock-in, but also extends the investment depreciation far back in time. By utilizing open hardware and low cost Arduino-based solutions, along with several sensor integra-tion and hardware modifications activities, we were able to develop a significantly lower cost wireless sensor network, targeted at small farms. The wireless sensor network is accompanied by software modules for management of the gathered values, as well as being able to communicate these measurements to other platforms via the web.

I2

Real-Time Cargo Vol-ume Recognition

Transport and logistics faces fluctuations in cargo volume that statistically can only be captured with a large error. Observing such dynamic volume fluctuations more effectively and providing the data about volume fluctuations in real-time promises many benefits for better management of transport processes, such as reducing unused transport capacity and ensuring timely delivery of cargo. We combine a mobile App with internet-connected (IoT) sensors to deliver up-to-date, timely, and precise information about parcel volumes inside containers. In particular, we introduce a novel approach for employing internet-connected low-cost, off-the-shelf 3D scanners (Microsoft kinect) for capturing and analys-ing actual cargo volumes. Accuracy of volume recognition as been evaluated in controlled experiments indicating that cargo volume can be measured with high accuracy. In addi-tion, a survey study with domain experts revealed its high potential for practical use.

7.4 Process Innovations

Name Summary

X1

Linked Pedigrees

An entirely new approach to tracking and tracing in the supply chain based on an inte-gration of GS1 standards with Semantic technology. Aston has formalised the GS1 EPCIS standard in a series of formally rigorous ontologies (EEM, CBV) and provides a Java library. Together with a rigorous architecture, this enables stakeholders along the supply chain to record events as "linked pedigrees" in individual separate triple stores which providing URL links to corresponding pedigrees upstream in the supply chain. This enables each stakeholder to keep complete control of their data while enabling total tracking, tracing and transparency to appropriately authorised stakeholders (e.g. regulators or retailers). The main benefit of this approach is opportunity for multiple software developers to provide light-weight but interoperable systems for data integra-tions across the supply chain

X2

Floriculture Logistic Label and Business Rules

When transporting flowers and plants, such as in the Netherlands, often an ‘auction delivery note’ is used. The delivery note identifies each load carrier and as such the flower or plant lots which are on that load carrier. More and more often however this auction delivery note is no longer used for the transport of flowers and plants. E.g. when delivering large lots from grower direct to retailer. Or deliveries of non-auction growers and the transport from one auction location to another location of lots bought via KOA (Remote Buying). And finally also the transport from the wholesale trader to his customers in the country and abroad. The innovation covers a set of business rules as to how these transports can be performed at best, building on the standard Floricul-ture Logistic Label.

FIspace 11.11.2015


Name Summary

X3

Predictive Transport Process Monitoring

Predictive business process monitoring aims at forecasting potential problems during process execution. Predictive business process monitoring thereby facilitates handling these problems proactively before they occur. We adapt and tune three main classes of predictive monitoring techniques to the problem of forecasting transport process instances. In particular, we show that machine learning, constraint satisfaction, and Quality-of-Service (QoS) aggregation can be used for transport prediction and that we can consistently achieve a prediction accuracy of more than 70%. To improve the pre-diction process, we exploit the characteristics of the individual techniques and define an ensemble of these techniques. Evidence indicates that this may, for instance, improve precision by 14% or recall by 23%.

FIspace 11.11.2015


7.5 Individual Innovations

The innovations as groups and listed before are presented in further detail in the following sections.

7.5.1 A1 – Improved Shopping Experience App

Summary of the innovation

The apps developed by CBT provide clients with a set of functionalities in just one app which will make their shopping experience much easier than before. All these functionalities have been developed in An-droid and iOS in order to obtain a better market acceptance. Consumers can manage their shopping lists by adding real products from the supermarket. Moreover, the app even suggests different recipes based on consumer preferences and health information. Consumers can access tailored product information at the supermarket via the mobile device by means of augmented reality. Furthermore, customers will re-ceive real time information from the supermarket about the best offers and alerts. What is more, they can send feedback about the products to the supermarket. All these app are a new product created by CBT that has been demonstrated to real customers in a real supermarket environment in Barcelona (Plusfresc) in June 2015 in order to obtain a complete application totally adapted to real users from all ages.

Key features / capabilities

Shopping list management: products can be added by voice recognition, barcode scanning or aug-mented reality technologies.

Recipes recommendations: customers will receive recommendations about recipes that could be interesting for them

Augmented Reality: customers will be able to visualize information (calories, origin, allergy info, etc.) superposed over the product they are scanning by means of their smartphone

Real time offers and alerts: customers will receive personalized offers and discounts, as well as alerts related to the health conditions of products

Feedback delivery: when users detect that there is a product in a bad condition, they can send an alert to the supermarket who could send them discounts back

Maturity level (TRL - Technology Readiness Level)

TRL 6 – technology demonstrated in relevant environment (industrially relevant environment in the case of key enabling technologies)

Availability

Video: https://youtu.be/aXQdsymHork

Apple store: https://itunes.apple.com/es/app/fispace-supermarket/id993202100?l=en&mt=8

Deliverable (report)

FIspace Deliverable D400.13: “Domain-specific test applications 3rd release”

Licensing

Free app in the Apple Store

Public domain (research papers)

Closed source (prototype code)

FIspace partner(s) that own innovation & contact points

CBT Comunicación y Multimedia S.L. [email protected]

https://youtu.be/aXQdsymHork

https://itunes.apple.com/es/app/fispace-supermarket/id993202100?l=en&mt=8

mailto:[email protected]

FIspace 11.11.2015


7.5.2 A2 – Fresh Food Transparency Apps


The innovative transparency system for meat has been developed based on the new EPCIS standard that can handle irrevocable events, e.g. a slaughtered cow can never become alive again or even one single piece as it was in the beginning. The system consists of one or more EPCIS repositories that con-tain all events of a meat item starting at the farm, and subsequently passing the slaughterhouse, meat processors, distributors and or cold store to arrive finally in the supermarket. At the end of the FIspace project the transparency system is a rather well tested prototype that forms the main result of the MIP trial.

The MIP trial transparency system may be extended to more meat supply chains and to other types of food, at a national base, in Europe or worldwide. Therefore there is a business perspective to introduce it in real food supply chains.


Query App: enables standard EPCIS query operations, i.e. queries about raw, intermediate or end-meat products for specific business locations, processes, time intervals, etc.

Aggregation App: collects and aggregates automatically traceability information about a given end or intermediate product and their presentation. This app will be based on the Query App and the Dis-covery App

Farm Capture App: is an easy to use web-page-like app to enable farmers to copy animal passport data (and more) as EPCIS events and master data on other aspects to an EPCIS repository.

Discovery App discovers which business party has information about a specific object, e.g. a product identified via Global Trade Item Number (GTIN).


TRL 4 – technology validated in lab

Availability

Research papers

Bartram, T., et al. (2014). Efficient Transparency in Meat Supply Chains with IT-Standards: EPCIS based Tracking & Tracing for Business Partners, Consumers and Authorities. IT-Standards in der Agrar- und Ernährungswirtschaft, Fokus: Risico- und Krisenmanagement, 34. GIL-Jahrestagung, 24-25 February 2014. M. Clasen, M. Hamer, S. Lehnert, B. Petersen and T. Brigitte. Bonn, Ge-sellschaft für Informatik e.V.: 185-188. http://www.gil-net.de/Publikationen/26_185-188.pdf

Scholten, H., et al. (2014). Enabling Transparency in Meat Supply Chains: tracking & tracing for supply chain partners, consumers and authorities. IT-Standards in der Agrar- und Ernährungs-wirtschaft, Fokus: Risico- und Krisenmanagement, 34. GIL-Jahrestagung, 24-25 February 2014. M. Clasen, M. Hamer, S. Lehnert, B. Petersen and T. Brigitte. Bonn, Gesellschaft für Informatik e.V.: 181-184. http://www.gil-net.de/Publikationen/26_181-184.pdf

Kassahun, A., et al. (2014). "Enabling chain-wide transparency in meat supply chains based on the EPCIS global standard and cloud-based services." Computers and Electronics in Agriculture 109: 179-190. DOI: 10.1016/j.compag.2014.10.002.

Kassahun, A., et al. (2015). Realizing chain-wide transparency in meat supply chains using web applications based on GS1 standards EFITA/WCCA/CIGR 2015 Conference, June 29 - July 2 2015. Poznan, Poland.

Deliverable (code/prototype)

The source code is in Java and owned by EECC

URL / link to repository FIspace platform http://www.fispace.eu/experimental-environment.html

Video

URL: http://www.eecc.info/files/mip/mip.html

Other

http://www.gil-net.de/Publikationen/26_185-188.pdf

http://www.gil-net.de/Publikationen/26_181-184.pdf

http://www.fispace.eu/experimental-environment.html

http://www.eecc.info/files/mip/mip.html

FIspace 11.11.2015


The MIP Trial aims at ensuring, that consumers, regulators and meat supply chain participants have reliable information concerning the origin of meat /a meat product (birth, breeding, slaughter-ing, deboning, processing, packaging). In general it is about enabling consumers to obtain better information on the goods they purchase and producers to better track the flow of goods to the consumers.

URL to flyer on platform http://www.fispace.eu/Documentations/Leaflets/meat-information-on--provenance-leaflet.pdf

Licensing

All apps are closed source, owned by the developer of the apps, EECC.


Wageningen University, Huub Scholten ([email protected])l and Ayalew Kassahun ([email protected])

GS1-Germany, Tim Bartram ([email protected]) and Sabine Kläser ([email protected])

European EPC Competence Center, Falk Nieder ([email protected])+ Nico Becker ([email protected])

7.5.3 A3 – Import and export of consumer goods Apps


This innovation is concerned with planning and execution of logistics activity in consumer goods sector ensuring effective planning of related activities resulting in improved coordination, loss minimization, effi-cient use of resources and high customer satisfaction level. Effective planning and timely monitoring of the transportation process is very crucial since unexpected delays might lead to many problems and losses in several stages starting from the production activity till the delivery of finished goods to the cus-tomers.


The trial is composed by a web app and two mobile applications that have the following key features:

Transport Demand Application (TD). The main functionality is to improve collaboration between different stakeholders during the transport demand description process and to make it available to users till the end of the execution of the shipment. The main benefits are:

Seamless collaboration on transport demand creation process

Monitoring the status of transport demand thanks the collaboration between the Transport De-mand App and the Shipment Status App

Notification management during transport order creation

Shipment Status Mobile Application (SS). The application improves the information exchange be-tween shippers and consigners during the transport execution process. The key strengths are:

Improved overview and visibility of stock in transit

Get notified on deviations and their impact (basis for decision making)

More effective and cost optimized deviation management

Improved end-to-end collaborative supply chain planning due to information from one source

Manual Event & Deviation Reporting Application (MEDR) allows the stakeholders that are re-sponsible from the execution of the transport process to report the events, status of the shipment and deviations during the execution process. The main benefits are:

Report the relevant information about ongoing transport processes in real-time to each involved stakeholder

Easily communicate with partners to coordinate activities

Reduction of manual effort for reporting status & deviations

http://www.fispace.eu/Documentations/Leaflets/meat-information-on--provenance-leaflet.pdf

http://www.fispace.eu/Documentations/Leaflets/meat-information-on--provenance-leaflet.pdf

mailto:[email protected])l






FIspace 11.11.2015



TRL 5: Large scale prototype tested in intended environment.

Availability

Research paper

FISpace site - IMPORT AND EXPORT OF CONSUMER GOODS http://www.fispace.eu


D400.1

D400.8

D400.12

FIspace-D400.12-Annex-10-D.455.42.1.1-2.1-3.1-FR-TransportShipmentEventDeviation-Apps-FINCONS.docx

D400.13

Licensing




FINCONS Spa

ARCELIK

7.5.4 A4 – CargoSwApp


In the short-sea container market, the carriers face problems as low visibility and predictability of the transport demand, low customer loyalty and a high number of late transport booking cancellations, mostly due to lack of collaboration or access to information. This results in short time windows to find new cargo,

extra work on re‐planning and sub‐optimal use of transport capacity. It is common that 30‐40% of cargo is cancelled close to the cut-off time. The CargoSwApp was developed to cope with these late cancelations and enable carriers to quickly react and find replacement. CargoSwApp also offers the possibility to as-sess each booking, and enable the carrier to anticipate cancellations, thus using overbooking in a more effective manner. By extending the scope of the CargoSwApp, functionalities for shippers have also been added: the possibility to search the marketplace via CargoSwApp and benchmark service offers at ship-ment level. CargoSwApp allows for immediate information exchange between shipper and carrier.


Matchmaking (Shipper publishes transport demand): The carrier receives the transport demand. The bid is sent directly from CargoSwApp. The carrier receives the booking status when the bid is ac-cepted or rejected.

Matchmaking (Carrier searches the marketplace): The carrier searches for transport demand and sends bids to fill up the ship and to find replacement for cancellations

Vessel capacity utilization chart: CargoSwApp is used by the carrier to get an overview of the ca-pacity utilization for each vessel, voyage and leg. The utilization chart links directly to a marketplace for sending relevant bids.

Anticipation of cancellation: The carrier gets detailed information about all bookings, included probability for cancellation and the current status.

Benchmarking of bids: The shipper reviews the bids from different carriers at one place.


FIspace 11.11.2015



TRL 3 – experimental proof of concept

Availability

Conference paper / Publication:

Rialland, A., & Hagaseth, M. (2014). Future Internet Based Services for Improved Transport Plan-ning and Capacity Utilization. International Maritime-Port Technology and Development Confer-ence (MTEC). Trondheim.

Deliverable (project reports)

FIspace Deliverable D400.5: Final report on trial experimentation and App development and up-dated plan for Phase 3 rollout, April 2015

FIspace Deliverable D400.13: Domain-Specific Test Applications Final Release, July 2015

Video demonstration

Online video presentation of the CargoSwApp, developed by MARINTEK and SDZ

Application:

Access to application: http://176.9.164.3/cargoswapp/

Information leaflet – Fish Distribution (Re-)planning trial description

http://www.fispace.eu/Documentations/Leaflets/fish-distribution-leaflet.pdf

Licensing




SDZ, DE - [email protected], [email protected]

MARINTEK, NO - [email protected], [email protected]

North-Sea Container line (NCL), NO – [email protected], [email protected]

7.5.5 A5 – Botanic Trading Information App


The prototype Botanic App offers valuable trading information to professional growers and traders in flowers and plants. It offers anytime and anywhere access to the correct taxonomic product descriptions, trading codes (VBN codes) and availability throughout the year.

Reduction of errors in communication and ordering is expected, which enhances the efficiency in the supply chain.


Growers and traders are informed on smartphone about:

Products that can be traded

Trade code to be used for unique identification of the product

Recently introduced products

Detailed botanical information

Availability pro month


TRL 5 – technology validated in relevant environment

http://176.9.164.3/cargoswapp/

http://www.fispace.eu/Documentations/Leaflets/fish-distribution-leaflet.pdf







FIspace 11.11.2015


Availability


D400.13

Licensing

Closed source, prototype


Q-ray BV Wageningen, The Netherlands

7.5.6 A6 – RISKMAN App - Risk Management in the Distribution of Fresh Food and Vegetables


RISKMAN significantly differs from other warning systems. RISKMAN offers a collection of structured (contracted laboratories, public authorities (i.e. EFSA)) and unstructured information items (i.e. social media networks) in order to provide a collection of potential information on risks in the distribution of fruits and vegetables to the users of the app (i.e. risk man-agers of agri-food companies). It therefore repre-sents a special and innovative type of news center for critical information on food safety, which we con-sider as an early warning system.


RISKMAN Cockpit: Collection summary of available potential information on risks in the distribution of fruits and vegetables empowers stakeholders to have fast access to sufficient information

RISKMAN Settings: Interface for customizing process and placement of information units (individually and tailor-made at the disposal of the user)



Availability


FIspace Deliverable D400.13: “ DomainApps-FFVTrial-RISKMAN”

Licensing



snoopmedia, Bonn, [email protected]

7.5.7 A7 – BizSLAM App – Business SLA Management


SLA management of transport and logistics services significantly differs from SLA management of cloud or web services due to the important role that frame SLAs play in contracting. A frame SLA is a general agreement that constitutes a long-term contract between parties. The terms and conditions of the frame SLA become the governing terms and conditions for all specific SLAs established under such a frame

FIspace 11.11.2015


SLA. Not considering the relationships between frame SLAs, specific SLAs and QoS monitoring infor-mation may lead to partial conclusions and decisions, thereby resulting in avoidable penalties. BizSLAM delivers a multi-level run-time SLA management approach for transport services that takes into account those relationships. BizSLAM is a cloud-based software component that automatically manages multi-level SLAs by extending SLA management solutions from service-oriented computing.


SLA Operations: online access and search to SLA information provided via FIspace platform; SLA data stored in BizSLAM is a subset of legal contract agreed by transport and logistics partners

SLA Analytics: real-time detection and signalling of SLA violations; differentiating between actual and potential violations at run-time



Availability

Research paper

C. Cassales Marquezan, A. Metzger, R. Franklin, and K. Pohl, “Runtime management of multi-level SLAs for transport and logistics services (industry paper),” in Int’l Conference on Service Oriented Computing (ICSOC 2014), Paris, France, November 3-6, 2014, X. Franch, A. Ghose, and G. Lewis, Eds., 2014. http://dx.doi.org/10.1007/978-3-662-45391-9_49

A. Gutierrez, C. Cassales Marquezan, M. Resinas, A. Metzger, A. Ruiz-Cortés, and K. Pohl, “Ex-tending WS-Agreement to support automated conformity check on transport & logistics service agreements,” in 11th Int’l Conference on Service-Oriented Computing (ICSOC), Berlin, Germany, December 2-5, ser. Lecture Notes in Computer Science, S. Basu, C. Pautasso, L. Zhang, and X. Fu, Eds., vol. 8274. Springer, 2013, pp. 567–574. http://dx.doi.org/10.1007/978-3-642-45005-1_47


FIspace Deliverable D400.9: “Initial Applications Third Release”

Licensing

Public domain (algorithms described in research papers)


paluno, University of Duisburg-Essen; [email protected]

7.5.8 A8 – Bad Weather Warning App


Different fumigation products have optimal application conditions, drying time, absorption rate and reten-tion time. For that reason, sprayer operators seek a lot of information about the weather and the environ-ment with of high accuracy (up to field level). To achieve this goal, the Workability Data App has design and develop an automated decision-making prediction module which shall help the farmers to decided the most suitable period for their spraying activities and notify them if the forecast prediction has changed. The App calculates the spraying conditions for a particular location based on the criteria specified by the farmer and the chosen dataset containing the weather predictions (wind speed / direction, probability / type and intensity of rainfall, temperature, humidity, etc). Once the spraying activity has been planned (using the scheduling app), this App module gathers the information in order to periodically check that the weather prediction updates don’t affect the scheduled activity workability. Depending on the preferred weather provider, the App can check the forecasts several times per hour. If the value changes signifi-cantly, for example not allowing for the execution of the spraying, this module will send a push notification

http://dx.doi.org/10.1007/978-3-662-45391-9_49

http://dx.doi.org/10.1007/978-3-642-45005-1_47

http://dx.doi.org/10.1007/978-3-642-45005-1_47


FIspace 11.11.2015


to the farmer mobile terminal and other selected platforms, reporting him about this unforeseen event. It allows re-starting the cycle if the farmer deemed it appropriate


Capability which will allow registered farmers to predict the most suitable period for their spraying activities based on the workability for each day-period for the following days through the correlation between the weather predictions and the weather criteria defined by the farmers.

Capability which will periodically warn farmers of unforeseen unfavourable weather conditions for their planned spraying activities.



Availability


D400.12

Video

https://www.youtube.com/watch?v=yTCYf4uxw78

Licensing

open source / CC


BOMO ([email protected], [email protected])

Wageningen UR ([email protected])

7.5.9 A9 – Traffic Light App


The Traffic Light App allows supermarket customers to access important information about certain prod-uct attributes they might find useful. The app shows in a clear way whether the attribute associated to the product is in a dangerous level, a normal level or a good level based on rules previously de-fined. An administrator can create and later update these rules if necessary.

The customer asks for information using the product id and sends the request to the server that searches for the product information and applies the rules. The information is then shown on the screen where each attribute is coloured in green, yellow or red based on whether it is considered good, normal or dan-gerous, respectively.

The innovation of this approach relies on the provision of rules in product information making the applica-tion configurable and adaptable to other conditions or food parameters.


Product scanner: responsible of scanning an image that contains a code, using the mobile camera. This capability parses the image and extracts the code that is sent to the Product Info Parser

Product info parser: retrieves product information from Product Info TIC (PITIC). Nutritional values are presented in Spanish as this information is directly provided by the supermarket.

Product info display: renders the visual information of the product for which product information has been requested.

https://www.youtube.com/watch?v=yTCYf4uxw78


FIspace 11.11.2015




Availability

Deliverables (report)

FIspace Deliverable D400.12 “Domain-Specific Test Applications 2nd Release” (to be published)

FIspace Deliverable D400.13 “Domain-specific test applications 3rd release” (to be published)

Licensing




This innovation is possible thanks to the collaboration between UPM, ATOS and PlusFresc. UPM devel-oped the application core and interface, ATOS developed the connection to FIspace platform and the back-end service that provided personalization functionality and PlusFresc provided product information and testing/validation activities with end-users in the supermarket.

UPM – Contact: Ramón Alcarria: [email protected]

ATOS – Contact: Javier Romero: [email protected]

PlusFresc – Contact: Marta Pascual: [email protected]

7.5.10 A10 – BOXMAN


BOXMAN is a first application that reaches beyond enterprise borders and realizes a chain encompassing management of packaging (crates, boxes) across the whole food chain reaching from production agricul-ture until retail. All enterprises are involved in reporting the movement of crates (in and out) while the central box management company assures that demand of boxes by enterprises are met at all times and that empty boxes are cleaned upon being returned by retail companies. Despite the chain encompassing management application, each company runs its own web-based application which is linked to the box management group.

The application provides transparency on the carriers of products which provides the basis for other ap-plications such as tracking and tracing of products, the identification of origin, the monitoring of product quality, etc.


Real time overview of our available RTI stock

Reduced loss and theft risk through a clear and transparent documentation.

Minimal documentation effort by sharing and reusing digital data.

No more unnecessary orders of RTIs, because you don’t know how full your RTI stock is.

On-Click-Transfer of your stock information to all your PMOs.


TRL 8 – system complete and qualified

Availability





FIspace 11.11.2015


D400.12 Domain-specific test applications 2nd

release

D400.13 Domain-specific test applications 3rd

release


Demo installation

https://boxman.iml.fraunhofer.de

Presentation

http://fispace.eu/boxman.html

Licensing

Closed Source


Martin Fiedler, Fraunhofer IML, [email protected]

Benedikt Mättig, Fraunhofer IML, [email protected]

7.5.11 A11 – Product: PIA (Product Information App)


PIA is an application that reaches beyond enterprise borders and realizes a chain encompassing ex-change of information between stakeholders across the whole food supply chain, reaching from produc-tion agriculture to retail.

This application provides a solution for many problems the food chains are presently experiencing. It pro-vides transparency across the chain on product characteristics, product quality, characteristics of produc-tion processes (e.g. inputs in agricultural production), logistics, tracking and tracing needs, and more. It also provides the basis for monitoring product quality and deliveries along the chain.

At retail, PIA provides the interface for applications that communicate information to consumers. Beyond its reach across the chain, its innovation is in the separation of the information exchange into a sequence of individual apps that are run by individual enterprises, i.e. it is not based on a central data management approach. The central data management approach of previous systems has been the core barrier for adoption of information exchange solutions by the food sector. This innovative approach, enabled by the FIspace platform, has the potential of being adopted by the sector beyond individual applications.


Capturing of initial product information as well as aggregation, disaggregation, adding and forwarding of product information with a fine-grained access control,

Receiving product information (accumulated along the supply chain) for incoming goods, providing quality feedback to suppliers, and offering the basis to communicate product information to consum-ers,

Secure exchange of quality-related product information between supply chain stakeholders, support-ing private data sources with access management,

Enabling a decentralised information storage, while also allowing a shared storage, just in accord-ance to end-user preferences,

Company confidential data can be made available as appropriate, taking into account requirements of business agreements with different partners or individual situations in the supply chain,

Establishing traceability by linking incoming and outgoing goods,

Facilitating data acquisition based on templates that can be created with respect to requirements of partners, products or transport conditions,

Master data management that is able to reflect most recent standards in terms of content and format.

https://boxman.iml.fraunhofer.de/

http://fispace.eu/boxman.html

FIspace 11.11.2015




Availability


D400.6 (PU) - Functionalities of Baseline Applications, section 2

D400.7 (PP) - Initial (Baseline) Applications 1st Release, section 3.1.1

D400.8 (PP) - Initial Applications 2nd

Release, section 3.1

D400.9 (PP) - Initial Applications Third Release, section 3.1

Overview of PIA on FIspace website


PIA prototype start widget deployed on the dashboard of a test user account in the Experimen-tation Environment

PIA prototype backend (provides also the PIA frontend) deployed on two servers

o https://pia-schorsch.fispace.eu:8443/ffv

o https://pia-ie.fispace.eu:8443/ffv

Publication

Sundmaeker, Harald; Einramhof, Peter; Systematic Heterogeneity: How to combine Smartphone related Apps with FIspace. Journal on Food System Dynamics, Vol 6(2); PP. 117-128; available at http://www.foodsystemdynamics.org/

Presentation

Poster and accompanying PowerPoint presentation at the ECFI 2, September 2014, Munich

Licensing



PIA has been developed by ATB - Institute for Applied Systems Technology Bremen GmbH (Germany). E-mail contacts:

Harald Sundmaeker <[email protected]>

Norman Gülcü < [email protected]>

Peter Einramhof <[email protected]>

7.5.12 A12 – Tailored Information for Consumers Initial App (TIC)


One of the trial concerns in the provisioning of accurate information to individual consumer´s needs. Product Info TIC app main objective is to collect and store links of the different product information pro-viders. This information is made available to other apps in the Trial like TaPIA of Traffic Light App, as well as other FIspace apps through the use of a Capability Type and a Capability added to the FIspace plat-form.


The product information is stored as URL links to the owner of the information

One product can have more than one link to product information.

All information from a product is packed in one predefined format when the information is requested.

Has been added the capability to store the feedback from consumers of a product.

http://fispace.eu/piaapp.html

https://pia-ie.fispace.eu:8443/ffv

http://www.foodsystemdynamics.org/




FIspace 11.11.2015


A FIspace Capability Type and a Capability have been provided in the FIspace platform to allow third party apps obtain product information from the app.



Availability


o D400.7 Baseline applications 1st release

o D400.8 Baseline applications 2nd release

o D400.9 Baseline applications 3rd release

o D400.13 Domain-specific test applications 3rd release

Licensing




ATOS Silvia Castellvi [email protected]

7.5.13 P1 – FIspace Studio


The Software Development Kit provides tool-support for the development of FIspace Apps. The SDK eases the work of App developers during the implementation of the Apps, providing specific tools and hiding the complexity of the platform. Also the Business Process architects find the proper way to manage the business entities at FIspace platform. The SDK for FIspace consists of a collection of Eclipse plugins available to be installed and the FIspace Studio Tool (which is the binary distribution of such plugins). Also, a set of libraries implemented in several programming languages provides the FIspace user with the appropriate tool to connect to the platform.

FIspace Studio Tool is represented by an Eclipse Rich Client Application. The distribution provides the required user interface for all of the pre-installed FIspace SDK functionalities along with a customized approach of the Eclipse IDE reaching the specific needs of FIspace platform.


FIspace wizard: generation of basic FIspace projects through maven archetypes (for widgets, backends, decoupled ones, compact projects, javaFX, RCP projects, and nodeJS).

OAuth client management: the user can create its own OAuth clients to access to FIspace platform.

FIspace Capability model: management of capability types, capabilities (also publication), business process template and business process.

Apps uploading: widgets and backends can be uploaded to FIspace platform in an easy way. Also the user can update the applications just uploaded.

B2B access: authoring of BCM and EPM configurations. The business architects can also manage the business process configurations creating, uploading, updating and removing from FIspace plat-form.


TRL 6– technology demonstrated in relevant environment (industrially relevant environment in the case of key enabling technologies)


FIspace 11.11.2015


Availability


FIspace Deliverable D200.1

FIspace Deliverable D200.5-FIspace_Integrated_Release_V2-v0.5

FIspace Deliverable D200.5-Annex_Front-End_User_Guide-v0.3

FIspace Deliverable D200.7

Licensing

Apache 2.0


ATOS :

Silvia Castellvi ([email protected])

Jordi Hernández ([email protected])

Miryam Villegas ([email protected])

UPM:

Ramón Alcarria ([email protected])

Diego Sánchez de Rivera ([email protected])

NKUA:

Dimitris Soukaras ([email protected])

7.5.14 P2 – Business process collaboration enhanced with complex event driven capabilities


In today’s competitive and dynamic landscape, business managers are continuously forced to effectively react to any event that has the potential to affect the expected course of their business processes. To cope with this requirement, companies are increasingly adopting business process engines alongside with event processing engines, to manage their business process and get real-time alerts once a situation requiring a course of action occurs. However, these two engines deal with different business logic and programming models and, as result, integration between the two is far from being easy. Business process engines are usually synchronous and the process encompasses sequential steps or tasks to be per-formed. Event processing engines are by nature asynchronous. Events can happen in any order and an action is taken in a reactive mode.

The B2B component in FIspace, composed of a business collaboration module (BCM) and a (complex) event processing engine (EPM), offers a seamless integration between these two types of engines. The artefact-centric approach for business processes is reactive and asynchronous, and events are the ones responsible for the progress in the flow. Moreover, the programming model of the BCM supports the in-clusion of events as a building block in the programming model making the integration easy. While the event logic is done within the EPM, the output events can be guards and milestones in the BCM pro-gramming model.

The B2B “packages” two types of engines while maintaining a clear separation between their two types of business logic, making it a unique potential product. As the two engines are generic, the B2B can be ap-plicable to any domain.


Generic approach for combining business processes and event-driven application, applicable to any domain – the engines are generic tools, as well as the method employed, making the approach appli-cable to any domain.






FIspace 11.11.2015


Event driven business processes – the business process evolves in an asynchronous way, dictated by events.

Joint Context lifecyle management – the lifecycle of “artifacts” and “events” are synchronized by Con-texts (one or more common attributes)

Separation of concerns between the event driven logic and business process logic – while this feature enables the implementation of sophisticated applications, the integration is still easy to do.

Business process template – The business process logic initializes the entire process and dictates the flow. The event-driven logic “enriches” the process in places when complex event processing is required, without introducing additional complexity in the process, just by including derived events from the EPM into the BCM. In addition, the event-driven logic can be customized and extended and therefore, customize the business process for specific cases.


TRL 5 – technology validated in relevant environment (industrially relevant environment in the case of key enabling technologies)

Availability

Research paper

F. Fournier and L. Limonad, “The BE2 model: When Business Events meet Business Entities”,

DAB14 Workshop, BPM 2014 International Workshops, Eindhoven, The Netherlands; 09/2014.

S. Barmpounakis, A. Kaloxylos, A. Groumas, L. Katsikas, V. Sarris, K. Dimtsa, F. Fournier, E. An-toniou, N. Alonistioti, and S. Wolfert, “Management & Control applications in Agriculture domain via a Future Internet Business-to-Business Platform”, Information Processing in Agriculture, Vol-ume 2, Issue 1, May 2015, Pages 51–63. DOI:10.1016/j.inpa.2015.04.002DOI. open access at: http://www.sciencedirect.com/science/article/pii/S2214317315000153


D200.2

D200.4

D200.6

D200.8


FIspace platform (open source)

Open source project

BCM (open source in Bitbucket project repositoty)

EPM (open source in Bitbucket project repositoty)

Licensing


Open source (Apache 2)


IBM Research – Haifa; [email protected]

7.5.15 P3 – Ygg: Capability-driven Cross-Organizational Business Collaboration


The core functionality of Ygg is to facilitate business to business collaboration. The main way Ygg sup-ports this is via business processes. Characteristic of these business processes is that they exceed the boundaries of one business. All Ygg core components are involved in supporting those business pro-cesses.


FIspace 11.11.2015


Some examples:

A farmer would like to get advice from an external adviser about the most efficient times to spray his crop for protection. The business process of a farmer getting his advice involves two separate busi-ness premises which interact with each other to get what they need in order to provide the service. The farmer asks for the advice and exposes some information about his field and crop so the adviser can retrieve them to give a proper advice to the farmer

An assembly factory orders some rough materials from another factory and asks a logistics provider to facilitate the transport. Placing the order, providing the logistics provider with the proper information all exceeds the boundaries of one business.

A business process in Ygg is implicit. This means you don't have to define or describe one explicitly. Us-ing the examples, the adviser only has to define in Ygg that he is capable of providing an advice. The

farmer can then in it's turn use this capability. This introduces the concept of capability.

For the farmer it would be very helpful if all capabilities providing similar services would look the same. That way the farmer would be able to switch from one adviser to the other without making a lot of adjust-

ments in his software. For this reason Ygg contains a registry with defined capability types.


Connecting service endpoints (capabilities)

Scalable microservice architecture connecting multiple service clouds



Availability

Online documentation: https://bitbucket.org/limetri/ygg/wiki/CapabilityModel

Source code available https://bitbucket.org/limetri/ygg

public instance running as part of Fispace SDI (EE)

Licensing

GPL V3.0


LimeTri ([email protected])

7.5.16 P4 – Composite Service Bus


The Composite Service Bus (CSB) layer of FISpace Operating Environment is the middleware that ena-bles integration of different FISpace service components and applications. CSB provides a set of integra-tion interfaces and qualities of service, required to support a wide spectrum of information exchange sce-narios, ranging from best effort notifications, to guaranteed delivery of transactional data. The Cloud Ser-vice Bus has virtually unlimited scalability, both in the number of supported end-points, and in the number of communication channels allowed by the Bus transport fabric.

The scalability challenge, posed by the large number of data producers, service providers and consumers in this cloud-based project, is addressed by Peer-to-Peer overlay technology. The CSB core is comprised of Bus Nodes, connected by a peer2peer structured overlay fabric. The CSB clients are the FISpace ser-vice components, using the Bus for integration and connectivity. This two-tier architecture allows us to build an enterprise-strength service bus, with extensive functionality set and assured delivery of transac-tional data.

https://bitbucket.org/limetri/ygg/wiki/CapabilityModel

https://bitbucket.org/limetri/ygg

FIspace 11.11.2015



Peer-to-Peer overlay

Queuing in peer-to-peer network

Synchronous Request/Response

Single Request/ Multiple Response mechanism

Time-limited asynchronous Request/Response



Availability


D200.7, “Operating Environment (260) components”


Short summary of format (code, binary, etc.) Source code, with dependency on a number of external jars

URL / link to repository https://bitbucket.org/fispace/csb

Licensing

The CSB is Open Source. Two basic components used by the CSB: SR and RUM remain IBM pro-prietary. However, we grant free unlimited usage of these components for users of the FIspace plat-form.


IBM Research – Haifa, [email protected]

7.5.17 I1 – Low Cost Wireless Sensor Network based on Open Hardware


To engage small-medium farmers into next generation agricultural processes, it is essential to present them with products and services that have as low entry cost as possible. To this end, a simple, effective and low cost wireless sensor network deployment was needed so that farmers will benefit the most from what a platform such as FIspace has to offer.

However it is often the case that sensor network equipment is really expensive and is only compatible with the vendors’ software management solution. This leads not only to vendor lock-in, but also extends the investment depreciation far back in time.

By utilizing open hardware and low cost Arduino-based solutions, along with several sensor integration and hardware modifications activities, we were able to develop a significantly lower cost wireless sensor network, targeted at small farms. The wireless sensor network is accompanied by software modules for management of the gathered values, as well as being able to communicate these measurements to other platforms via the web.


Low Cost Wireless Sensor Network: Several medium ready solutions were integrated together in order to bring down the cost of the hardware deployment.

Easily extensible: Introducing new network nodes to the network is done through a plug and play manner.

FIspace 11.11.2015


Data Management: The Wireless Sensor Network is accompanied by management software re-sponsible for collecting the measurements, storing them, presenting them to the user, and communi-cating them to other systems if needed.



Availability


WP 400 deliverables

Code available on FIspace Apps repository.

Licensing

FIspace license


NKUA (Sokratis Barmpounakis, [email protected] )

Innovators (Makis Stamatelatos, [email protected])

7.5.18 I2 – Real-Time Cargo Volume Recognition


Transport and logistics faces fluctuations in cargo volume that statistically can only be captured with a large error. Observing such dynamic volume fluctuations more effectively and providing the data about volume fluctuations in real-time promises many benefits for better management of transport processes, such as reducing unused transport capacity and ensuring timely delivery of cargo. We combine a mobile App with internet-connected (IoT) sensors to deliver up-to-date, timely, and precise information about parcel volumes inside containers. In particular, we introduce a novel approach for employing internet-connected low-cost, off-the-shelf 3D scanners (Microsoft kinect) for capturing and analysing actual cargo volumes. Accuracy of volume recognition as been evaluated in controlled experiments indicating that cargo volume can be measured with high accuracy. In addition, a survey study with domain experts re-vealed its high potential for practical use.


Mobile App for uniquely identifying parcel containers

Volume recognition algorithm to compute cargo volume from 3D sensor data (Microsoft kinect)



Availability

Research paper

F. Föcker, A. Neubauer, A. Metzger, G. Gröner, and K. Pohl, “Real-time cargo volume recognition using internet-connected 3D scanners,” in 10th Int’l Conference on Evaluation of Novel Ap-proaches to Software Engineering (ENASE), Barcelona, Spain, April 29-30, J. Filipe and L. Maciaszek, Eds., 2015.

Licensing

Public domain (algorithms described in research papers; experimental data set)



FIspace 11.11.2015




7.5.19 X1 – Linked Pedigrees


Linked Pedigrees is an entirely new approach to tracking and tracing in the supply chain based on an integration of GS1 standards with Semantic technology. Aston has formalised the GS1 EPCIS standard in a series of formally rigorous ontologies (EEM, CBV) and provides a Java library. Together with a rigorous architecture, this enables stakeholders along the supply chain to record events as "linked pedigrees" in individual separate triple stores which providing URL links to corresponding pedigrees upstream in the supply chain. This enables each stakeholder to keep complete control of their data while enabling total tracking, tracing and transparency to appropriately authorised stakeholders (e.g. regulators or retailers). The main benefit of this approach is opportunity for multiple software developers to provide light-weight but interoperable systems for data integrations across the supply chain. This is completely novel work.


Facilitates complete tracking and tracing across the supply chain while allowing individual control of data.

Built around existing standards (EPCIS of GS1, RDF, OWL, Java) while entirely extensible as new data fields are added to EPCIS or new knowledge is required and can be added by extending the on-tologies.

Open source implementation available with MIT licence.

Java library is enterprise ready, capable of integration with existing or new systems

Generic architecture applicable to most supply chain domains, including agriculture, processed food, pharmaceuticals, and any manufactured product.



Availability

Research paper

Monika Solanki and Christopher Brewster. OntoPedigree: A content ontology design pattern for traceability knowledge representation in supply chains. Semantic Web – Interoperability, Usability, Applicability. Semantic Web Journal. bibtex

Monika Solanki and Christopher Brewster. Enhancing visibility in EPCIS governing Agri-food Sup-ply Chains via Linked Pedigrees. International Journal on Semantic Web and Information Sys-tems. Vol 10:3. bibtex

Open Source project

https://github.com/nimonika/LinkedEPCIS

Presentation

http://www.slideshare.net/nimonika/linked-data-driven-epcis-eventbased-traceability-across-supply-chain-business-processes

cf. Other presentations here: http://www.slideshare.net/nimonika

Licensing

Open Source MIT License for the software. Use of EPCIS is governed by GS1.


Aston University, Christopher Brewster [email protected]


http://cbrewster.com/papers/Solanki_SWJ15.pdf

http://cbrewster.com/papers/Solanki_SWJ15.pdf

http://cbrewster.com/papers/Solanki_SWJ15.txt

http://cbrewster.com/papers/Solanki_IJSWIS15.pdf

http://cbrewster.com/papers/Solanki_IJSWIS15.pdf

http://cbrewster.com/papers/Solanki_IJSWIS15.txt

https://github.com/nimonika/LinkedEPCIS



http://www.slideshare.net/nimonika


FIspace 11.11.2015


Aston University, Monika Solanki (now moved to Oxford [email protected] )

7.5.20 X2 – Floriculture logistic label and business rules


When transporting flowers and plants in the Netherlands often an ‘auction delivery note’ is used. The delivery note identifies each load carrier and as such the flower or plant lots which are on that load carri-er.

More and more often however this auction delivery note is no longer used for the transport of flowers and plants. E.g. when delivering large lots from grower direct to retailer. Or deliveries of non-auction growers and the transport from one auction location to another location of lots bought via KOA (Remote Buying). And finally also the transport from the wholesale trader to his customers in the country and abroad.

Together with the concerning parties from the sector and GS1, Floricode has set up business rules as to how these transports can be performed at best. Therefore it is necessary to use the standard Floriculture Logistic Label.


Using the international GS1 SSCC standard for labels

In combination with electronic data exchange

Improvement of the logistic process

Applicable for all kind of scanners and applications

Applicable for all types of customers inside and outside the supply chain of flowers and plants



Availability


GS1 label; manual for despatch units and packages in the Floriculture sector (available in Dutch and English)

http://www.floricode.com/en-us/coding/floriculturelogisticlabelsscc.aspx

http://www.floricode.com/nl-nl/coderen/sierteeltlogistieklabelsscc.aspx

Licensing

The report is free available

Software developers for the floricultural industry can apply for the Floricode message standards

SSCC codes can be obtained at GS1


Floricode, Roelofarendsveen Netherlands: [email protected]

GS1, Amstelveen Netherlands


FIspace 11.11.2015


7.5.21 X3 – Predictive Transport Process Monitoring


Predictive business process monitoring aims at forecasting potential problems during process execution. Predictive business process monitoring thereby facilitates handling these problems proactively before they occur. We adapt and tune three main classes of predictive monitoring techniques to the problem of forecasting transport process instances. In particular, we show that machine learning, constraint satisfac-tion, and Quality-of-Service (QoS) aggregation can be used for transport prediction and that we can con-sistently achieve a prediction accuracy of more than 70%. To improve the prediction process, we exploit the characteristics of the individual techniques and define an ensemble of these techniques. Evidence indicates that this may, for instance, improve precision by 14% or recall by 23%.


Prediction of completion time of running transport process instances

Ensemble prediction to fine-tune prediction accuracy depending on application situation



Availability

Research paper

A. Metzger, P. Leitner, D. Ivanovi c, E. Schmieders, R. Franklin, M. Carro, S. Dustdar, and K. Pohl, “Comparing and combining predictive business process monitoring techniques,” IEEE Trans. on Systems Man Cybernetics: Systems, vol. 45, no. 2, pp. 276–290, 2015. http://dx.doi.org/10.1109/TSMC.2014.2347265

A. Metzger, R. Franklin, and Y. Engel, “Predictive monitoring of heterogeneous service-oriented business networks: The transport and logistics case (best paper award: service engineering inno-vation & quality),” in Service Research and Innovation Institute Global Conference (SRII 2012), ser. Conference Publishing Service (CPS), R. Badinelli, F. Bodendorf, S. Towers, S. Singhal, and M. Gupta, Eds. IEEE Computer Society, 2012, pp. 313–322. http://dx.doi.org/10.1109/SRII.2012.42

Other

Industry data set of transport processes (Cargo 2000); http://www.s-cube-network.eu/c2k

Licensing

Public domain (algorithms described in research papers; industrial data set)



http://dx.doi.org/10.1109/TSMC.2014.2347265

http://dx.doi.org/10.1109/SRII.2012.42

http://www.s-cube-network.eu/c2k


FIspace 11.11.2015


8 Section A (public) – Use and Dissemination of Foreground

8.1 Listing of Dissemination Activities

The FIspace members have published specifically the following papers during the reporting period that shall be highlighted:

Poppe, K. J., Wolfert, J., Verdouw, C. N., & Renwick, A. (2015). A European perspective on the economics of Big Data. Farm Policy Journal, 12(1), 11-19.

Wolfert, J., Sørensen, C. G., & Goense, D. (2014). A future internet collaboration platform for safe and healthy food from farm to fork. Global Conference (SRII), 2014 Annual SRII (pp. 266 - 273). San Jose, CA, USA: IEEE.

Verdouw, C. N., Beulens, A. J. M., & Wolfert, J. (2014). Towards Software Mass Customiza-tion for Business Collaboration. Global Conference (SRII), 2014 Annual SRII (pp. 106 - 115): IEEE.

Poppe, K., Wolfert, J., & Verdouw, C. N. (2014). How ICT is changing the nature of the farm: a research agenda on the economics of big data. Proceedings of the 11th European IFSA Symposium, 1-4 April 2014 in Berlin, Germany. Berlin.

Kruize, J. W., Wolfert, J., Goense, D., Scholten, H., Beulens, A. J. M., & Veenstra, T. (2014). Integrating ICT applications for farm business collaboration processes using FIspace. Global Conference (SRII), 2014 Annual SRII (pp. 232 - 240). San Jose, CA, USA: IEEE.

Kassahun, A., R. J. M. Hartog, T. Sadowski, H. Scholten, T. Bartram, J. Wolfert and A. J. M. Beulens (2014). "Enabling chain-wide transparency in meat supply chains based on the EP-CIS global standard and cloud-based services." Computers and Electronics in Agriculture 109: 179-190. DOI: 10.1016/j.compag.2014.10.002.

Metzger, P. Leitner, D. Ivanovic, E. Schmieders, R. Franklin, M. Carro, S. Dustdar, and K. Pohl, “Comparing and combining predictive business process monitoring techniques,” IEEE Trans. on Systems Man Cybernetics: Systems, 2014. http://dx.doi.org/10.1109/TSMC.2014.2347265

Cassales Marquezan, A. Metzger, R. Franklin, and K. Pohl, “Runtime management of multi-level SLAs for transport and logistics services (industry paper),” in Int’l Conference on Ser-vice Oriented Computing (ICSOC 2014), Paris, France, November 3-6, 2014, X. Franch, A. Ghose, and G. Lewis, Eds., 2014.

Gutierrez, C. Cassales Marquezan, M. Resinas, A. Metzger, A. Ruiz-Cortes, and K. Pohl, “Ex-tending WS-Agreement to support automated conformity check on transport & logistics service agreements (short paper),” in ICSOC 2013, 2013.

Z. Feldmann, F. Fournier, R. Franklin, and A. Metzger, “Industry article: Proactive event pro-cessing in action: A case study on the proactive management of transport processes,” in Proceedings of the Seventh ACM International Conference on Distributed Event-Based Sys-tems, DEBS 2013, Arlington, Texas, USA, S. Chakravarthy, S. Urban, P. Pietzuch, E. Runden-steiner, and S. Dietrich, Eds. ACM, 2013, pp. 97–106.

On top of that, FIspace partners have participated in a number of related events, conferences and trade shows, prepared additional publications and press releases, organized workshops in conferences. A number of these events have been highlighted in FI PPP newsletters and FIWARE website news section (https://www.fiware.org/news/). All this information in detail can be found in the following Table 6.

FIspace 11.11.2015


Table 6: FIspace dissemination activities in the second/ final reporting period and beyond.

Date Type/ Description/ Title Audience Countries addressed

Size of Audi-ence

Partner re-sponsible/ involved

11.04.2013 Turkish FI Day, Istanbul Academia, Research, Industry

Turkey 90 Bülent Erbaş, Haluk Gök-men

17-18.04.2013

Multimodal Transport Event, Las Palmas

Academia, Research, Industry

Europe 350 Gonzalo Pe-rez Rodriguez

16.04.2013 Lecture at Wageningen Uni-versity

Academia, Research

The Neth-erlands

32 Huub Schol-ten

24.-25.04.2013

1st Stakeholder Meeting

FFV Trial Industry, IT Developer

Germany 30 CentMa, ATB, Euro Pool

29-30.04.2013

G-8 International Conference on Open Data for Agriculture, Washington D.C.


Global 250 Sjaak Wolfert

08-10.05.2013

FIA Week Dublin,

FI-PPP Opening Plenary Presentation: “FIspace: En-gage and build the next ’killer’ FI Application”

Researchers, Business people

Europe, overseas

600

Ana Garcia, Christopher Brewster, Andreas Metzger, Bü-lent Erbaş, Haluk Gök-men

15.05.2013 Fruit & Vegetable Expert Group on Standards, GS1 Germany

Industry, NGO

Germany 50 Euro Pool

27.05.2013

AgroConncet (Dutch Agro ICT Standardisation Society); FI-space info afternoon, Wa-geningen

Food Indus-try, Web developers, ICT enter-preneurs

The Neth-erlands

35 Krijn Poppe, Sjaak Wolfert

28-29.05.2013

Korea Days, Istanbul Academia, Research, Industry

Korea, Europe, Turkey

210 (50, 60, 100)

Bülent Erbaş, Haluk Gök-men, Rob Fitzpatrick

4-5.06.2013

IoT Conference Shanghai Academia, Research, Industry

Global 1500-1750

Sjaak Wolfert

6.06.2013

Fruit & Vegetables and The Flowers & Plants industry joint stakeholder event, LogIxperi-ence in Venlo

Industry Germany, The Neth-erlands

30 DLO, Euro-Pool

13-14.06.2013

4th European Summit on the Future Internet


Europe 80 Haluk Gök-men

13.06.2013 Era-Net Transport, Info Day and Brokerage Event



26.06.2013 FI-PPP Infoday Phase 3, Eindhoven (organised by Min-

Regional development

The Neth-erlands

40 Krijn Poppe (EU: Arian

FIspace 11.11.2015



Size of Audi-ence


istery of Economic Affairs) organisa-tions, Tech parks, Incu-bators

Zwegers)

23-27.06.2013

World Conference of the Euro-pean Federation for Infor-mation Technology in Agricul-ture, Food and the Environ-ment (EFITA), Turin


Global 250

Sjaak Wolfert, Gerhard Schiefer Invit-ed keynote speech

27-28.06.2013

SRII Europe Leadership Summit


Global 115

Sjaak Wolfert, Eliezer Dekel, Rod Franklin, Bülent Erbaş, Andreas Metzger

29.06-03.07.2013

PUBLICATION:

“Industry article: Proactive event processing in action: A case study on the proactive management of transport pro-cesses,” in Proceedings of the Seventh

ACM International Conference on Distributed Event-Based Systems, DEBS 2013, Arling-ton, Texas, USA,

S. Chakravarthy, S. Urban, P. Pietzuch, E. Rundensteiner, and S. Dietrich, Eds. ACM, 2013


Global ~250

Z. Feldmann, F. Fournier, R. Franklin, and A. Metzger

17.07.2013 Presentation to Euro Pool Shareholder Group

Industry Nether-lands

10 Euro Pool

18.07.2013

Presentation: Overview of FIspace project, Real-time and Embedded Systems Forum, Philadelphia, USA

Industry, Academia

Europe, USA, Ja-pan

29 The Open Group

22-25.07.2013

International Farm Manage-ment Conference, Warsaw


Global 250-300

Invited key-note speech, Gerhard Schiefer

20.08.2013 FI-PPP Info Day, Istanbul Academia, Research, Industry


21.08.2013 FI-PPP Info Day, Ankara Academia, Research, Industry


20.08.2013 FI-PPP Info Day, Izmir Academia, Research, Industry


3-7.09.2013

Campus Party Web entre-preuneurs,

Europe & World

3500-5000

ARC/Haluk Gökmen

FIspace 11.11.2015



Size of Audi-ence


developers,

11.09.2013 FIspace Press Conference-Release

General, ICT and Finance Media

Turkey 10

Sjaak Wolfert, Ahmet İhsan Ceylan, Bülent Erbaş, Özgür Çetinoğlu,

17-18.09.2013

InfoDay and Brokerage Event “Innovative Partnerships and Future Internet Development in the Enlarged EU, https://ec.Europe.eu/digital-agenda/en/innovative-partnerships-and-future-internet-development-enlarged-eu


Europe & Poland

>100 Sjaak Wolfert, Bülent Erbaş, Ana Garcia

19-22.09.2013

6th International Conference on Information and Communi-cation Technologies in Agricul-ture, Food and Environment (HAICTA 2013), http://2013.haicta.gr/

Academia, Research

Greece & Europe

200-250

OPEKEPE / Marona Katsikou, Kostas Kountouris, Roxanne Apostolou

19-22.09.2013

6th International Conference on Information and Communi-cation Technologies in Agricul-ture, Food and Environment (HAICTA 2013), http://2013.haicta.gr/

Tutorial “Semantic Web and Ontologies in Agrifood”

Academia, Research

Greece & Europe

15

Christopher Brewster, Daniel Martini, Monika Solanki

25.09.2013 Open call phase 2 Information day

Academia, Developers, SME, Indus-try

Europe ~100

Elies Prunes, Haluk Gök-men, Andreas Metzger, Huub Schol-ten

01.10.2013

A short description of the FISpace Project and the MIP Trial on the Website of GS1 Germany as well with linkage to the FIspace Website.


Germany, Europe

NA GS1 G

01.10.2013

MIP Trial flyers: printed and digital forms. The digital copy in two versions: with and with-out Open Call info.

Stakeholder of the meat supply chain and IT com-panies

Europe 100 WU, GS1 G

03.10.2013 Infoday call Phase 3 obj. 1.8 “Expansion of Use Cases”

Academia, Research, Industry, RDAs

Europe 100-200

Elies Prunes, Krijn Poppe, Bülent Erbaş, Haluk Gök-men, Huub Scholten, Tim Bartram, Ana

https://ec.europe.eu/digital-agenda/en/innovative-partnerships-and-future-internet-development-enlarged-eu





http://2013.haicta.gr/

http://2013.haicta.gr/

FIspace 11.11.2015



Size of Audi-ence


Garcia, Pieter Ballon

04.10.2013 Infoday call Phase 3 obj. 1.9 “TF Extension and Usage”

Academia, Research, Industry,

Europe ~100

Sjaak Wolfert,

Bülent Erbaş, Ana Garcia, Haluk Gök-men

11.10.2013

Presentation “Digital Agricul-ture and Food and the FI-PPP”, presentation for DCA BoerEnBusiness, Lelystad

Agricultural media, Sup-ply industry, Food indus-try

NL 60 Krijn Poppe

15.10.2013

European Conference on Agri-cultural Entrepreneurship “This farm is your own business” www.farmsup.eu

Academia, Research, Industry, Farmers

Greece, Europe

380

OPEKEPE / Marona Katsikou, Pa-raskevi Kon-tou

15.10.2013 Business Community Meat, GS1 Germany

Industry, NGO


17.10.2013 Smart Rural Projects Exhibition

Research, Industry, municipal representa-tives

Spain 150 Plusfresc

28-30.10.2013

NEM Summit 2013, Nantes Academia, Research, Industry


01.11.2013 MIP Trial Article in the maga-zine “RFID im Blick”


Germany NA GS1

04.11.2013 FI-Workshop at Bonn.realis Industry, NGO, Sci-ence


05.11.2013

Infoday Open Call FIspace and Phase-3 information

LEI Wageningen UR, Agro-Connect and Floricode

Web entre-preneurs Sme in ICT

NL ?

Sjaak Wolfert, Cor Verdouw; Krijn Poppe, Henk Zwinkels

14.11.2013

Congress Frugicom (Standard organisation in Fruit and Veg). Presentation on Digital Agricul-ture and the FI-PPP, Bleiswijk

Entrepre-neurs in hor-ticulture, ict companies

NL ? Krijn Poppe, Cor Verdouw

27.-29.11.2013

2nd

Stakeholder Meeting FFV Trial

Industry, IT Developer

Germany 20 CentMa, ATB, Euro Pool

03.12.2013 MIP Trial Article in the GS1 STANDARDS magazine


Global NA GS1

05.11.2013 Lecture at Wageningen Uni-versity

Academia Nether-lands

20 Ayalew Kassahun

6- ICT Event 2013, Vilnius Academia, Lithuania ~3500 Ana Garcia,

http://www.farmsup.eu/

FIspace 11.11.2015



Size of Audi-ence


8.11.2013 Research, Industry

Sjaak Wolfert, Bülent Erbaş, Michael Zahl-man, Andreas Metzger, Ha-luk Gökmen, Evrim Özgül

15-16.11.2013

2. R&D Centres’ Summit Academia, Research, Industry

Istanbul, Turkey

>500

Evrim Özgül, Hande Koç,

Bülent Erbaş, Haluk Gök-men

28.11.2013

XIFI workshop in conjunction with FOKUS FUSECO forum, http://www.fokus.fraunhofer.de/en/fokus_events/ngni/fuseco_forum_2013/index.html


Europe 300 Sjaak Wolfert

28-30.11.2013

TIM (Turkish Exporters As-sembly) Innovation Week

Academia, Research, Industry, General Pub-lic

Istanbul, Turkey, Global

>15000

ARCELIK, KOC SISTEM, Burcu Özgür, Bülent Erbaş

2-5.12.2013

PUBLICATION:

Extending WS-Agreement to Support Automated Conformity Check on Transport & Logis-tics Service Agreements. Pro-ceedings of 11th International Conference on Service Orient-ed Computing (ICSOC 2013)

Berlin, Germany,


Global ~200

UDE / Antonio Manuel Gutierrez , Clarissa Cas-sales Marquezan, Manuel Resinas, An-dreas Metz-ger, Antonio Ruiz-Cortés, and Klaus Pohl.

9.12.2013 3

rd Conference of the Greek

National Rural Network (NRN) “Networking and Innovation”

Academia, Industry, State repre-sentatives

Greece ~50 Kostantinos Kountouris

January 2014

Info day

(13 in total in various dates of January)

Scientists from the fields of Agri-culture, To-pography, Economics and Informat-ics working .

Greece ~600 OPEKEPE

23-01-2014 Floricode annual user meeting Floriculturale industry

Nether-lands

250 DLO-LEI, M&A, Floricode

http://www.fokus.fraunhofer.de/en/fokus_events/ngni/fuseco_forum_2013/index.html



FIspace 11.11.2015



Size of Audi-ence


30.January-02.February. 2014

AGROTICA FAIR 2014 - The 25th International Fair For Agricultural Machinery, Equipment & Supplies, Thes-saloniki, Greece, 1

st February

FIspace session

Agricultural sector, In-dustry, Sci-ence, Aca-demia

30 coun-tries

125,000 visitors (1000 FIspace leaflets distrib-uted)

OPEKEPE stand in the fair

05.-07.02.2014

Fruit Logistica, International Trade Fair on Fruits & Vegeta-bles

Industry Germany 20 Euro Pool

17.-21.02.2014

8 th International European Forum (Igls-Forum) - (139th EAAE Seminar) on

System Dynamics and Innova-tion in Food Networks

Innsbruck-Igls, Austria

Academia Internation-al

80 CentMa, ATB, Euro Pool

24.02.2014 FI-Workshop at GIL-Jahrestagung 2014, Bonn

Academia, Science, Industry

Germany 30 Robert Reiche Euro Pool

24.-25.02.2014

GIL Conference: „IT-Standards in Agrifood“

Bartram, T., H. Scholten, A. Kassahun, S. Kläser, R. Trö-ger, R.J.M. Hartog, A. Schil-lings-Schmitz and S. Meier, 2014. Efficient Transparency in Meat Supply Chains with IT-Standards: EPCIS based Tracking & Tracing for Busi-ness Partners, Consumers and Authorities. 34. GIL-Jahrestagung, 24-25 February 2014. GIL, Bonn.


Germany ~100

Tim Bartram, Huub Schol-ten, Daniel Martini, Esther Mietzsch

12.03.2014 Info day at SEPVE ( Associa-tion of Computer Science En-terprises of Northern Greece)

Industry Greece ~150 NKUA, OPEKEPE

18-20.03.2014

FIA Week, Athens and work-shop “FI-driven Digital Busi-ness Innovation”


Europe 600

Haluk Gök-men, Adrie Beulens, Ferhad Erdoğan

31.03.-02.04.2014

KTBL days 2014 Academia, Research, Industry

Germany 150

Daniel Martini, Robert Reiche, Timon Veenstra

FIspace 11.11.2015



Size of Audi-ence


2-3. April 2014

1st European Conference

on the Future Internet, (1.ECFI), Brussels, Belgium http://www.ecfi.eu/brussels2014/


Europe 250

Ana Garcia, Haluk Gök-men, Sjaak Wolfert, Har-ald Sundmaeker, Heritiana Ranaivoson, Pieter Ballon

2-4. April 2014

IFSA conference, Berlin, Ger-many (conference on Systems Research in Agriculture), Pa-per on ICT and FIspace,

http://ifsa.boku.ac.at/cms/index.php?id=133

Academia, Research

Europe 200 Krijn Poppe

7-8. April 2014

Koç Technology Board Annual Assembly

Industry, Academia, Research

Europe 100

Hande Koç, Haluk Gök-men, Ferhad Erdoğan, Mehmet Önat

10. April 2014

AES (Agricultural Economics Society) annual conference, Paris, France Paper on ICT and FIspace, http://www.aes.ac.uk/page.asp?ID=3

Academia, Research

UK + France

200 Krijn Poppe

23-25. April 2014

Annual SRII Global Confer-ence 2014, Silicon Valley, San Jose, CA, USA, http://www.thesrii.org/index.php/conference/2014-global-conference


Global ~300 Sjaak Wolfert

April/May 2014

Article on MIP in PROZEUS NL and on PROZEUS Webpage

Industry, SMEs

Germany NA GS1 G

6-9. May 2014

IST-Africa 2014, Mauritius, Industry, Academia, Research

Africa-Europe

~250 DLO

May 2014 Demonstration of FIspace platform to national project on transport and logistics (LoFIP)

Research, Industry

Germany 20 Andreas Metzger

27 May 2014

NESSI Summit 2014, Brus-sels, Belgium http://www.nessi-europe.eu/ ?Page=nessi_summit_2014

Industry, Academia, Research, Policy Mak-ers

Europe 80 Andreas Metzger

http://www.ecfi.eu/brussels2014/

http://www.ecfi.eu/brussels2014/



http://www.aes.ac.uk/page.asp?ID=3

http://www.aes.ac.uk/page.asp?ID=3

http://www.thesrii.org/index.php/conference/2014-global-conference



http://www.nessi-europe.eu/%20?Page=nessi_summit_2014

http://www.nessi-europe.eu/%20?Page=nessi_summit_2014

FIspace 11.11.2015



Size of Audi-ence


26-29. May 2014

8th ACM International Confer-

ence on Distributed Event Based Systems (DEBS14), Mumbai, India. Accepted Tuto-rial: “The Internet of Every-thing”, http://www.cse.iitb.ac.in/debs2014/


Global 80

IBM: Sarit Arcushin, Fabiana Four-nier, Opher Etzion

29-30. May 2014

Innovation Week Izmir, Turkey http://www.turkiyeinovasyonhaftasi.com/tr/etkinlik-hakkinda-gecmis-etkinlikler-2014ten-kalanlar.html


Turkey with Internation-al participa-tion

3200 H.Gökmen-ARC

June 2014

Enabling Self Organising Lo-gistics on the Web of Things. Position paper for the W3C Workshop on the Web of Things 2014

Industry Europe 100 Aston

June 2014

Linked data Driven, EPCIS Event Based Traceability in Supply

Chains

Industry, Academia

Europe 120 Aston

4-5. June 2014

Horizon 2020 National Launch Event – Istanbul, Turkey, FIn-est/FIspace success story presentation, http://www.h2020.org.tr/tr/haber/horizon-2020-turkiye-ulusal-acilis-konferansi-basariyla-tamamlandi

Industry, Academia, Research, Policy Mak-ers

Europe 900 H. Gökmen, E.Özgül (ARC)

15-19 June 2014

Intern. Conference of the In-ternational Food and Agribusi-ness Management Associa-tion, Cape Town, South Africa (www.ifama.org )

Academia, Industry

Global 500 CentMa

17-18. June 2014

Presentation of MIP Trial and Fispace in general

Research, Industry

Europe ~300 DLO, WU, GS1 G

18-19 .June 2014

SmartAgriMatics 2014, Paris, France, http://www.smartagrimatics.eu/


Global ~150

Sjaak Wolfert, Harald Sundmaeker, Ana Garcia, Annelise De Smet, Robert Reiche, Huub Scholten, Krijn Poppe, Haluk Gökmen, OPEKEPE, MARINTEK, ATOS, Plus-fresc, open call partners

http://www.cse.iitb.ac.in/debs2014/

http://www.cse.iitb.ac.in/debs2014/

http://www.turkiyeinovasyonhaftasi.com/tr/etkinlik-hakkinda-gecmis-etkinlikler-2014ten-kalanlar.html




http://www.h2020.org.tr/tr/haber/horizon-2020-turkiye-ulusal-acilis-konferansi-basariyla-tamamlandi




http://www.ifama.org/

http://www.smartagrimatics.eu/

FIspace 11.11.2015



Size of Audi-ence


22-25. June 2014

Research paper at 25th Euro-

pean Regional Conference of the International Telecommu-nication Society, Brussels, Belgium

http://www.itseurope.org/pdf/programme/Programme8.5.2014.pdf

Academia, Industry

Europe 150-200 iMinds

June 2014 3

rd Stakeholder Meeting

FFV Trial Industry Germany 30

CentMa, ATB, Euro Pool

27-30.

July 2014

World Conference on Comput-ers in Agriculture and Natural Resources, Costa Rica (www.wcca2014.org )

Academia, Industry

Global 200 DLO, CentMa

August 2014

Article in GS1 Austria Custom-er Magazine, http://www.gs1.at/downloads

Industry, Retail

Austria NA GS1 G

19-21. Au-gust 2014

EPCIS event based traceability in healthcare supply chains via automated generation of linked pedigrees at SemTechBiz, San Jose, USA

http://semtechbizsj2014.semanticweb.com/agenda.cfm ?con-fid=82&scheduleDay= 08/20/14


Global 400 Aston

26-29. August 2014

European Association of Agri-cultural Economists, Ljublijana, Slovenia (http://www.eaae2014.si/ )

Academia Europe 400 DLO, CentMa

September 2014

Modelling and Linking trans-formations in EPCIS governing supply chain business pro-cesses at EC-Web 2014, Germany, http://link.springer.com/chapter/10.1007%2F978-3-319-10491-1_5


Global 200 Aston

September 2014

Detecting EPCIS Exceptions in linked traceability streams across supply chain business processes at SEMANTiCS 2014, Germany


Global 200 Aston

2-5. Sep-tember 2014

Open Living Lab Days 2014, http://openlivinglabdays14.com/ ,Amsterdam, Netherlands

Academia, Research, Industry, Policy Mak-ers

Global 300 Ana Garcia

5. Septem-ber 2014

SOUL-FI Meeting, Porto, Por-tugal

Academia, Industry, Research

Europe 200 Eloi Montcada (Plusfresc)




http://www.wcca2014.org/

http://www.gs1.at/downloads

http://semtechbizsj2014.semanticweb.com/agenda.cfm%20?confid=82&scheduleDay=%2008/20/14




http://www.eaae2014.si/

http://link.springer.com/chapter/10.1007%2F978-3-319-10491-1_5



http://openlivinglabdays14.com/

http://openlivinglabdays14.com/

FIspace 11.11.2015



Size of Audi-ence


6-14 Sep-tember 2014

79th TIF THESSALONIKI IN-TERNATIONAL FAIR, Thessa-loniki, Greece, http://tif.helexpo.gr/tif/en

Industry, SME’s, Academia, Policy Mak-ers

Greece, Global

200,000 OPEKEPE

8. Septem-ber 2014

3rd Workshop on Data and Artifact Centric,Haifa, Israel Paper title: “The BE

2 model:

When Business Events meet Business Entities, Authors: Fabiana Fournier and Lior Limonad, https://sites.google.com/site/dab32014/

Research, Industry

Israel 20 Fabiana Four-nier, Lior Limonad

September 2014

Opportunities in Phase 3, Stakeholder Info Day, FFV Trial

Industry Germany 100 CentMa, ATB, Euro Pool

12 Sep-tember 2014

Phase 3 Accelerator Workshop of FInish and SpeedUpEurope for Entrepreneurs about FI-WARE and FIspace

Industry, Research

Germany 50 ATB


2. ECFI, Munich, Germany, http://www.ecfi.eu/munich2014/


Germany 600

ARC, iMinds, DLO, CentMa, ATB, Euro Pool, KOC, IBM, UDE, GS1 G, WP400 team


ECR Tag 2015 „Transform now! Channel Management in der Value Chain 4.0“, Bonn, Germany, http://www.ecrtag.de/


Europe 950 Tim Bartram, Sabine Kläser

02. October 2014

Journal article: Enabling chain-wide transpar-ency in meat supply chains based on the EPCIS global standard and cloud-based services.

doi:10.1016/j.compag.2014.10.002


World Poten-tially many

Ayalew Kassahun, Rob Hartog, Huub Schol-ten and Adrie Beulens (WU); Tim Sadowski and Tim Bar-tram (GS1G); Sjaak Wolfert (LEI)

6-9. Octo-ber 2014

9th Conference of the Asian Federation for Information Technology in Agriculture, Perth, Australia, http://asicta.org/AFITA2014/


Asia 250 CentMa

7. October 2014

Matchmaking event FIspace “Smart Apps for Food & Flow-ers” Monster, The Netherlands


The Neth-erlands

120 Q-ray, DLO, Floricode

http://tif.helexpo.gr/tif/en

https://sites.google.com/site/dab32014/

https://sites.google.com/site/dab32014/

http://www.ecfi.eu/munich2014/

http://www.ecfi.eu/munich2014/

http://www.ecrtag.de/

http://asicta.org/AFITA2014/

FIspace 11.11.2015



Size of Audi-ence


9-10. October 2014

ICT Proposers' Day, Florence, Italy, http://ec.europa.eu/digital-agenda/en/ict-proposers-day-9-10-october-2014


Europe ~3000 ARC, KOC

15-17 October 2014

MULTI-SITE FIWARE EVENT: Connecting cities to the Inter-net of the Future Seville , Valencia, Las Palmas de Gran Canaria, Spain, http://www.fi-ware.org/multisiteevent/


Spain 200 Atos, Plus-fresc,

21. October 2014

EPCIS event based traceability in pharmaceutical supply chains via automated genera-tion of linked pedigrees at ISWC 2014, Riva del Garda, Trentino, Italy http://www.slideshare.net/nimonika/iswc2014-40532507 , http://iswc2014.semanticweb.org/


Global 600 Aston

27.-28. October 2014

Dynamic Business Collabora-tion in Supply Chains with Future Internet technologies: Acceleration of SME-driven App Development; Sundmaeker, Harald; Verdouw, Cor; IoTaaS, Inter-national Conference on IoT as a Service; Rome, Italy


Global 30 ATB, DLO

27-29. October 2014

Paper and presentation at the International Maritime and Port Technology and Development Conference, Trondheim, Nor-way http://www.mtec-conf.org/ "Future Internet Based Services for Improved Transport Planning and Capacity Utilization", and "Future Internet Enabled Ship-Port Coordination”


Global 70

Agathe Rialland, Marianne Hagaseth, Asmund Tjora

November 2014

A knowledge driven approach towards the validation of ex-ternally acquired traceability datasets in supply chain busi-ness processes at EKAW 2014

Industry, Research, Academia

Global 400 Aston

3-6. November 2014

12th International Conference on Service Oriented Compu-ting (ICSOC 2014), Paris, France, http://www.icsoc.org/


Global 200 UDE

http://ec.europa.eu/digital-agenda/en/ict-proposers-day-9-10-october-2014



http://www.fi-ware.org/multisiteevent/

http://www.fi-ware.org/multisiteevent/

http://www.slideshare.net/nimonika/iswc2014-40532507

http://www.slideshare.net/nimonika/iswc2014-40532507

http://iswc2014.semanticweb.org/

http://iswc2014.semanticweb.org/

http://www.mtec-conf.org/

http://www.icsoc.org/

FIspace 11.11.2015



Size of Audi-ence


04-06. November 2014

Industry Paper: “Runtime management of multi-level SLAs for transport and logis-tics services” in Int’l Confer-ence on Service Oriented Computing (ICSOC 2014), Paris, France, November 3-6, 2014, X. Franch, A. Ghose, and G. Lewis, Eds., 2014.

Research, Industry

Internation-al

200

C. Marquezan (UDE), A. Metzger (U-DE), K. Pohl (UDE)

7. Novem-ber 2014

Presentation: “Predictive Ana-lytics for Service-oriented Business Processes”, IFIP Working Group “Services-Oriented Systems”, Annual Meeting, Paris, France. No-vember, 2014.

Research Internation-al

15 A. Metzger (UDE)


Smart City Expo, World Con-gress, Barcelona, Spain, http://www.smartcityexpo.com/en/


Global 9000 ATOS, iMinds


NESSI Member’s and Interna-tional Cooperation Day, Barce-lona, Spain, http://www.nessi-eu-rope.eu/?page=eventsdetails&listID=9&rowID=495


Global 110 UDE, ARC

24. November 2015

Keynote presentation and panel discussion: “Big Data Value: Opportunities and Val-ue Add: The Future Logistics Example”, ComIn Talk, Essen, Germany

Research, Industry, SMEs

Germany 30 A. Metzger (UDE)

November 2014

Presentation at Conference: EuroID in Frankfurt/Main

Industry, Solution Providers

Germany NA GS1 G

November 2014

4th Stakeholder Meeting

FFV Trial Industry Germany 30

CentMa, ATB, Euro Pool

December 2014

Journal Article: “Comparing and combining predictive busi-ness process monitoring tech-niques,” IEEE Trans. on Sys-tems Man Cybernetics: Sys-tems, 2014. http://dx.doi.org/10.1109/TSMC.2014.2347265

Research, Industry

Internation-al

Tbd

A. Metzger (UDE), P. Leitner (U Zurich), D. Ivanovic (UPM), E. Schmieders (UDE), R. Franklin (KN), M. Carro (UPM), S. Dustdar (TU Vienna), K. Pohl (UDE)

http://www.smartcityexpo.com/en/


http://www.nessi-europe.eu/?page=eventsdetails&listID=9&rowID=495






FIspace 11.11.2015



Size of Audi-ence


4-6. December 2014

Innovation Week Istanbul http://www.turkiyeinovasyonhaftasi.com/tr/istanbul-2014-etkinlik-programi.html


Turkey with Internation-al participa-tion(Netherlands Part-ner Coun-try)

Over 40.000

ARC (Main Sponsor of the Event)

December 2014, Feb-ruary 2015

Opportunities in Phase 3 info days with Phase 3 projects


European Countries

500 to 1000

ARC, KOC, ATB, DLO, GS1 G, Euro Pool, iMinds

22 January 2015

Consumer workshop presenta-tion of TIC apps

Lleida, Spain

Industry Spain 20 Plusfresc

22. January 2015

SIERTEELT(DIGI)TAAL (‘Flo-riculture digital’), Floricode annual conference,

“FISpace APP’s for the regis-tration of the plant quality in the supply chain”

http://www.floricode.com/en-us/floricode/actueel/events/naslagwerk.aspx

Industry Europe 200

R. Robbe-mond (WUR-LEI),

H. Zwinkels Floricode

22 January 2015

Connected Smart Cities Con-ference, Brussels, Belgium

http://www.eventbrite.com/e/connected-smart-cities-conference-tickets-14661965333


Europe 120 ARC, iMinds, ENoLL

4-6. February 2015

Fruit Logistica 2015, Berlin, Germany, http://www.fruitlogistica.de/en/ Booth Presentation + Q&A

Industry Germany 200 Euro Pool

09-13 February 2015

GS1 Global Forum, Brussels, Belgium http://forum.gs1.org/

GS1 Global Member Organisa-tions

Global 600 GS1 Germany

9-13. February 2015

9 th International European Forum (Igls-Forum) - (139th EAAE Seminar) on System Dynamics and Innovation in Food Networks, Innsbruck-Igls, Austria, http://www.fooddynamics.org/


80 CentMa, Euro Pool

http://www.turkiyeinovasyonhaftasi.com/tr/istanbul-2014-etkinlik-programi.html










http://www.fruitlogistica.de/en/

http://www.fooddynamics.org/

FIspace 11.11.2015



Size of Audi-ence


15. Febru-ary 2015

Systematic Heterogeneity: How to combine Smartphone related Apps with FIspace. Harald Sundmaeker, Peter Einramhof; Journal on Food System Dynamics, Vol 6(2); ISSN 1869-6945 http://www.foodsystemdynamics.org/; Presented at 9th Inter-national European Forum on System Dynamics and Innova-tion in Food Networks; Inns-bruck-Igls, Austria; pp. 117-128


200 ATB

15. Febru-ary 2015

A Farm Information Model for Development and Configura-tion of Interoperable ICT Com-ponents to support Collabora-tive Business Processes – a case of late blight protection; Kriuze et al.; Journal on Food System Dy-namics, Vol 6(2); ISSN 1869-6945 http://www.foodsystemdynamics.org/; Presented at 9th Inter-national European Forum on System Dynamics and Innova-tion in Food Networks; Inns-bruck-Igls, Austria; pp. 276-284


200 DLO; WUR

23-24. February 2015

35. GIL-Jahrestagung, Kom-plexität versus Bedienbarkeit, Mensch-Maschine-Schnittstellen, Geisenheim, Germany (http://www.gil-net.de/Tagung/472.pdf)


Germany 90 CentMa

10-11.March. 2015

ITEA & ARTEMIS Co-summit, Berlin (Germany)

https://artemis-ia.eu/co-summit-2015/index.html


Global 300-400 KOC, UDE

16-19. March. 2015

Milan Global Entrepreneurship Congress (GEC)

http://eventegg.com/gec-2015/

Entrepre-neurs, Investors, Industry

Worldwide 3000 ENoLL





http://www.gil-net.de/Tagung/472.pdf

http://www.gil-net.de/Tagung/472.pdf



http://eventegg.com/gec-2015/

FIspace 11.11.2015



Size of Audi-ence


18. March 2015

Future Internet in Horizon 2020: how to build a pan-European framework to sup-port Innovation in SMEs" Summit, Rome, Italy

https://www.fi-xifi.eu/ news/eventview/article/future-internet-in-horizon-2020-how-to-build-a-pan-european-framework-to-support-innovation-in-smes.html


Europe 100-150 ATOS

25-26. March 2015

Net Futures 2015, Brussels, Belgium (former annual Future Internet Assembly-FIA Event), http://netfutures2015.eu/


Europe 600

DLO, ATB, KOC, IBM, UDE, ARC, ATOS, ENoLL, NKUA

1. April 2015

Biennale International Design Saint-Etienne 2015, France; Business Design session http://www.biennale-design.com/saint-etienne/2015/fr/home/


Global

~5,000 (100 partici-pants at session)

ENoLL, Grigoris Chat-zikostas – FRACTALS Accelerator

29-30 April 2015

Research Paper Presentation: F. Föcker, A. Neubauer, A. Metzger, G. Gröner, and K. Pohl, “Real-time cargo volume recognition using internet-connected 3D scanners,” in 10th Int’l Conference on Eval-uation of Novel Approaches to Software Engineering (EN-ASE), Barcelona, Spain, J. Filipe and L.Maciaszek, Eds., 2015.

Academia, Research

Internation-al

120 UDE

May 18-24 2015

37th International Conference on Software Engineering


Internation-al

900 UDE

May 2015

Information Processing in Ag-riculture Journal, Volume 2, Issue 1, May 2015, Pages 51–63,

http://www.sciencedirect.com/science/article/pii/S2214317315000153

Research, Academia

Global N/A

Sokratis Barmpouna-kis, Alexand-ros Kaloxylos, Aggelos Gro-umas, et al.

17-19 June 2015

BDVA 2015 Madrid Summit, Madrid, Spain http://www.bdva.eu/


Europe 350 UDE

https://www.fi-xifi.eu/%20news/eventview/article/future-internet-in-horizon-2020-how-to-build-a-pan-european-framework-to-support-innovation-in-smes.html






http://netfutures2015.eu/

http://www.biennale-design.com/saint-etienne/2015/fr/home/






http://www.bdva.eu/

FIspace 11.11.2015



Size of Audi-ence


June 29 - July 3 2015

Research Paper Presentation: C. Reinartz, A. Metzger, and K. Pohl, “Model-based Verifi-cation of Event-driven Busi-ness Processes,” in 9th Int’l Conference on Distributed Event-Based Systems (DEBS), Oslo, Norway, June 29 - July 3, F. Eliassen, R. Vitenberg, R. Friedman, and D. Eyers, Eds. ACM, 2015.

Academia, Research

Internation-al

200 UDE

25-28. August 2015

OpenLivingLab Days 2015-01-26, Turkey, Istanbul

http://www.openlivinglabs.eu/event/openlivinglab-days-2015

Academia, Research, Industry, Policymakers

Global ~170 ENoLL, Ar-celik

31. August 2015

Data- & Artifact-Centric BPM 4th Workshop Organizer, Innsbruck, Austria, https://sites.google.com/site/dabws2015/

Academia, Research

Global 50 Fabiana Four-nier IBM

2. Septem-ber 2015

FIspace Technical Workshop Accelerators, SMEs

Europe 25 All partners

23-24. September 2015

Conference “ECR Tag 2015”, Bonn, Germany, http://www.ecrtag.de/

Industry, Retail

Germany 1.000 GS1 G

September 2015

Annual Survey Industry, Retail

Germany 3.500 GS1 G

2. October 2015

Workshop on “State of the art technologies in next genera-tion data networks”, "Future Internet Space: Cloud-enabled IoT data management for Smart Farming, tracing and business request matching",

PCI 2015, 19th Panhellenic Conference on Informatics


Greece ~150

Sokratis Barm-pounakis, NKUA

5-6. Octo-ber 2015

Horizon 2020 Workshop, Bur-sa, Turkey


Turkey ~200 Arcelik

8-9. October 2015

Conference on Turkish Univer-sities in the European Re-search Area (ERA), Ankara, Turkey


Europe ~500 Arcelik

12-13. October 2015

Horizon 2020 Bridging Days, Izmir Turkey


Turkey ~250 Arcelik



https://sites.google.com/site/dabws2015/

https://sites.google.com/site/dabws2015/

http://www.ecrtag.de/

FIspace 11.11.2015



Size of Audi-ence


20 – 22 October 2015

ICT 2015 Innovate, Connect, Transform, Lisbon, Portugal

http://ec.europa.eu/digital-agenda/en/ict2015-innovate-connect-transform-lisbon-20-22-october-2015


Europe ~5000 Arcelik, UDE, ATOS, Koc, IBM

4-7 November 2015

ECFI 2015 – 3rd European Conference on the Future In-ternet in Hamburg

http://www.ecfi.eu/

Startups, Investors, Industry, Academia, Research

Europe >400

DLO, ATB, UDE, ATOS, Arcelik, iMinds, ENoLL


European Data Forum 2015

http://2015.data-forum.eu/

Industry, Researchers, Policymakers

Europe ~700 UDE, ATOS, Arcelik


Smart City Expo, World Con-gress, Barcelona, Spain


Industry, Policy Mak-ers, Research, Municipalities

Global ~9000 ENoLL, ATOS

7-10 De-cember 2015

7th European Innovation Summit, Brussels, Belgium

http://www.knowledge4innovation.eu/7th-european-innovation-summit-7-10-december-2015

Industry, Policy Mak-ers, Research,

Europe 500 Arcelik

2015

Business Process Manage-ment Workshops, Springer Book, Fabiana Fournier (Edi-tor) http://www.springer.com/us/book/9783319158945

Academia, Research

Global N/A Fabiana Four-nier(Editor) IBM





http://www.ecfi.eu/

http://2015.data-forum.eu/






http://www.springer.com/us/book/9783319158945

http://www.springer.com/us/book/9783319158945

FIspace 11.11.2015


9 Section B: Confidential Information

9.1 Part B1 – Applications for Patents, Trademarks, Registered Designs etc.

In the scope of the Fispace project there were no applications for patents, trademarks, registered de-signs, etc..

9.2 Part B2 – Report on societal implications

A General Information (completed automatically when Grant Agreement number is entered.

Grant Agreement Number: 604 123

Title of Project: FIspace: Future Internet Business Collaboration Networks in Agri-Food, Transport and Logistics

Name and Title of Coordinator: Harald Sundmaeker

B Ethics

1. Did your project undergo an Ethics Review (and/or Screening)?

If Yes: have you described the progress of compliance with the relevant Ethics Re-view/Screening Requirements in the frame of the periodic/final project reports?

Special Reminder: the progress of compliance with the Ethics Review/Screening Requirements should be described in the Period/Final Project Reports under the Section 3.2.2 'Work Progress and Achievements'

No

2. Please indicate whether your project involved any of the following issues (tick box) :

Research on Humans

Did the project involve children? No

Did the project involve patients? No

Did the project involve persons not able to give consent? No

Did the project involve adult healthy volunteers? No

Did the project involve Human genetic material? No

Did the project involve Human biological samples? No

Did the project involve Human data collection? No

Research on Human embryo/foetus

Did the project involve Human Embryos? No

Did the project involve Human Foetal Tissue / Cells? No

Did the project involve Human Embryonic Stem Cells (hESCs)? No

FIspace 11.11.2015


Did the project on human Embryonic Stem Cells involve cells in culture? No

Did the project on human Embryonic Stem Cells involve the derivation of cells from Embryos? No

Privacy

Did the project involve processing of genetic information or personal data (eg. health, sexual lifestyle, ethnicity, political opinion, religious or philosophical conviction)?

No

Did the project involve tracking the location or observation of people? No

Research on Animals

Did the project involve research on animals? No

Were those animals transgenic small laboratory animals? No

Were those animals transgenic farm animals? No

Were those animals cloned farm animals? No

Were those animals non-human primates? No

Research Involving Developing Countries

Did the project involve the use of local resources (genetic, animal, plant etc)? No

Was the project of benefit to local community (capacity building, access to healthcare, educa-tion etc)?

No

Dual Use

Research having direct military use No

Research having the potential for terrorist abuse No

C Workforce Statistics

1. Workforce statistics for the project: Please indicate in the table below the number of people who worked on the project (on a headcount basis).

Type of Position Number of Women Number of Men

Scientific Coordinator

Work package leaders

Experienced researchers (i.e. PhD holders)

PhD Students

Other

2. How many additional researchers (in companies and universities) were recruited specifically for this project?

Of which, indicate the number of men:

D Gender Aspects

5. Did you carry out specific Gender Equality Actions under the project? X

Yes

No

FIspace 11.11.2015


6. Which of the following actions did you carry out and how effective were they?

Not at all

effective

Very

effective

X Design and implement an equal opportunity policy X X Set targets to achieve a gender balance in the workforce X Organise conferences and workshops on gender X Actions to improve work-life balance X Other:

1. Was there a gender dimension associated with the research content – i.e. wherever people were the focus of the research as, for example, consumers, users, patients or in trials, was the issue of gender considered and addressed?

Yes- please specify

X No

E Synergies with Science Education

2. Did your project involve working with students and/or school pupils (e.g. open days, participa-tion in science festivals and events, prizes/competitions or joint projects)?

Yes- please specify

X No

3. Did the project generate any science education material (e.g. kits, websites, explanatory book-lets, DVDs)?

X Yes- please specify

Website, Webinar, Demos, Videos

No

F Interdisciplinarity

4. Which disciplines (see list below) are involved in your project?

X Main discipline4: 1.1

X Associated discipline4: 4.1 Associated discipline4:

G Engaging with Civil society and policy makers

11a Did your project engage with societal actors beyond the research community? (if 'No', go to Question 14)

X

Yes

No

11b If yes, did you engage with citizens (citizens' panels / juries) or organised civil society (NGOs, patients' groups etc.)?

No

Yes- in determining what research should be performed

X Yes - in implementing the research

X Yes, in communicating /disseminating / using the results of the project

11c In doing so, did your project involve actors whose role is mainly to organise the dialogue with citizens and organised civil society (e.g. professional mediator; communication company, science museums)?

X

Yes

No

4 Insert number from list below (Frascati Manual).

FIspace 11.11.2015


12. Did you engage with government / public bodies or policy makers (including international or-ganisations)

No

Yes- in framing the research agenda

Yes - in implementing the research agenda

X Yes, in communicating /disseminating / using the results of the project

13a Will the project generate outputs (expertise or scientific advice) which could be used by policy makers?

Yes – as a primary objective (please indicate areas below- multiple answers possible)

X Yes – as a secondary objective (please indicate areas below - multiple answer possible)

No

13b If Yes, in which fields?

13c If Yes, at which level?

Local / regional levels

National level

X European level

International level

H Use and dissemination

14. How many Articles were published/accepted for publication in peer-reviewed journals?

To how many of these is open access5 provided?

How many of these are published in open access journals?

How many of these are published in open repositories?

To how many of these is open access not provided?

Please check all applicable reasons for not providing open access:

X publisher's licensing agreement would not permit publishing in a repository

no suitable repository available

no suitable open access journal available

no funds available to publish in an open access journal

lack of time and resources

lack of information on open access

other6: ……………

15. How many new patent applications (‘priority filings’) have been made?

("Technologically unique": multiple applications for the same invention in different jurisdic-tions should be counted as just one application of grant).

-/-

16. Indicate how many of the following Intellectual Prop-erty Rights were applied for (give number in each box).

Trademark -/-

5 Open Access is defined as free of charge access for anyone via Internet. 6 For instance: classification for security project.

FIspace 11.11.2015


Registered design -/-

Other -/-

17. How many spin-off companies were created / are planned as a direct result of the project?

-/-

Indicate the approximate number of additional jobs in these companies:

18. Please indicate whether your project has a potential impact on employment, in comparison with the situation before your project:

Increase in employment, or X In small & medium-sized enterprises

X Safeguard employment, or In large companies

Decrease in employment, None of the above / not relevant to the project

Difficult to estimate / not possible to quantify

19. For your project partnership please estimate the employment effect resulting directly from your participation in Full Time Equivalent (FTE = one person working fulltime for a year) jobs:

Difficult to estimate

Indicate figure:

X

I Media and Communication to the general public

20. As part of the project, were any of the beneficiaries professionals in communication or media relations?

Yes X No

21. As part of the project, have any beneficiaries received professional media / communication train-ing / advice to improve communication with the general public?

Yes X No

22 Which of the following have been used to communicate information about your project to the general public, or have resulted from your project?

X Press Release X Coverage in specialist press

Media briefing Coverage in general (non-specialist) press

TV coverage / report X Coverage in national press

X Radio coverage / report Coverage in international press

X Brochures /posters / flyers X Website for the general public / internet

X DVD /Film /Multimedia X Event targeting general public (festival, confer-ence, exhibition, science café)

23 In which languages are the information products for the general public produced?

Language of the coordinator X English

Other language(s)

Question F-10: Classification of Scientific Disciplines according to the Frascati Manual 2002 (Proposed Standard Practice for Surveys on Research and Experimental Development, OECD 2002):

FIspace 11.11.2015


FIELDS OF SCIENCE AND TECHNOLOGY

1. NATURAL SCIENCES

1.1 Mathematics and computer sciences [mathematics and other allied fields: computer sciences and other allied subjects (software development only; hardware development should be classified in the engineering fields)]

1.2 Physical sciences (astronomy and space sciences, physics and other allied subjects)

1.3 Chemical sciences (chemistry, other allied subjects)

1.4 Earth and related environmental sciences (geology, geophysics, mineralogy, physical geography and other geosciences, meteorology and other atmospheric sciences including climatic research, oceanography, vulcanology, palaeoecology, other allied sciences)

1.5 Biological sciences (biology, botany, bacteriology, microbiology, zoology, entomology, genetics, biochemistry, biophysics, other allied sciences, excluding clinical and veterinary sciences)

2 ENGINEERING AND TECHNOLOGY

2.1 Civil engineering (architecture engineering, building science and engineering, construction engi-neering, municipal and structural engineering and other allied subjects)

2.2 Electrical engineering, electronics [electrical engineering, electronics, communication engineering and systems, computer engineering (hardware only) and other allied subjects]

2.3. Other engineering sciences (such as chemical, aeronautical and space, mechanical, metallurgical and materials engineering, and their specialised subdivisions; forest products; applied sciences such as geodesy, industrial chemistry, etc.; the science and technology of food production; spe-cialised technologies of interdisciplinary fields, e.g. systems analysis, metallurgy, mining, textile technology and other applied subjects)

3. MEDICAL SCIENCES

3.1 Basic medicine (anatomy, cytology, physiology, genetics, pharmacy, pharmacology, toxicology, immunology and immunohaematology, clinical chemistry, clinical microbiology, pathology)

3.2 Clinical medicine (anaesthesiology, paediatrics, obstetrics and gynaecology, internal medicine, surgery, dentistry, neurology, psychiatry, radiology, therapeutics, otorhinolaryngology, ophthal-mology)

3.3 Health sciences (public health services, social medicine, hygiene, nursing, epidemiology)

4. AGRICULTURAL SCIENCES

4.1 Agriculture, forestry, fisheries and allied sciences (agronomy, animal husbandry, fisheries, forest-ry, horticulture, other allied subjects)

4.2 Veterinary medicine

5. SOCIAL SCIENCES

5.1 Psychology

5.2 Economics

5.3 Educational sciences (education and training and other allied subjects)

5.4 Other social sciences [anthropology (social and cultural) and ethnology, demography, geography (human, economic and social), town and country planning, management, law, linguistics, political sciences, sociology, organisation and methods, miscellaneous social sciences and interdiscipli-

FIspace 11.11.2015


nary , methodological and historical S1T activities relating to subjects in this group. Physical an-thropology, physical geography and psychophysiology should normally be classified with the nat-ural sciences].

6. HUMANITIES

6.1 History (history, prehistory and history, together with auxiliary historical disciplines such as ar-chaeology, numismatics, palaeography, genealogy, etc.)

6.2 Languages and literature (ancient and modern)

6.3 Other humanities [philosophy (including the history of science and technology) arts, history of art, art criticism, painting, sculpture, musicology, dramatic art excluding artistic "research" of any kind, religion, theology, other fields and subjects pertaining to the humanities, methodological, histori-cal and other S1T activities relating to the subjects in this group]

FIspace Project Final Report - Europa · FIspace Project Final Report WP 100 Project Acronym &...

Documents

Transcript of FIspace Project Final Report - Europa · FIspace Project Final Report WP 100 Project Acronym &...