consolidate trials and identify business demands for ... · consolidate trials and identify...

D200.1 Consolidated FI Architecture for Perishable Supply Chains

Consolidate Trials and Identify Business De-mands for Matchmaking

WP 200

Accelerator Project: FInish

Full Title: Food Intelligence and Information Sharing for Business Collaboration enabled by the Future Internet

Grant Agreement No.: 632 857

Start date of the project: September, 1st 2014

Duration: 24

Status: Final

Document Identifier: FInish - D200.1 - FI-Architecture

Date: 31.10.2014

Revision: 008

Project website address: http://www.FInish-project.eu

FInish 24.10.2014

FInish-D200.1-FI-Architecture-Final of 46

Project Summary

The Finish project will sub-grant small and medium sized enterprises (SMEs) as well as web-entrepreneurs that are proposing the development of new software applications that are utilising FIWARE technologies and specifically the FIspace platform.

This shall result in the development and operation of intelligent systems for dynamic supply chains of perishable products such as food and flowers. Therefore, envisaged developments shall address the domains of agri-food supply chain, transport, logistics, food manufacturing/processing and/or retail of food/flowers. Potential synergies with other fields like e.g. smart cities, health awareness and/or multime-dia are welcome and shall be highlighted to see additional potentials of a proposed solution.

The FInish project is aiming at the sub-granting of proposals that have a clear business impact. There-fore, proposers shall identify and clearly outline the following:

Business needs of user communities and

Creative ideas & technological opportunities for the software SME/ web-entrepreneur.

Finish recommends addressing regional clusters that include close synergies with regional developments & policies that are embedded in European networks to assure a large reach out and business success after developing the proposed solution. To facilitate the provision of software services to a critical mass of developers and end-users, FInish promotes the usage of the FIspace platform. This homogeneous plat-form will compile apps in its app store, while allowing for their combined/synergetic usage. This shall spe-cifically enlarge the number of services/applications available in the FIspace store as a whole.

Therefore, it is the objective of FInish to enable seamless B2B collaboration for end-users and empower related companies including SMEs and new players to set up and participate in new regional, horizontal and vertical collaboration quickly and at minimal costs. By supporting this, FInish wants to promote an impulse to the shift from cost-driven to value-based, information-rich supply chains, which will significantly increase the added value, competiveness and sustainability of the domain.

More specifically, FInish aims to:

1. Empower small & innovative ICT players to develop high-quality and high-impact solutions for food and flower supply chain networks based on FIWARE technologies.

2. Develop a large set of innovative and technologically challenging services and applications for virtualisation, connectivity and intelligence of food and flower supply chain networks.

3. Implement and validate the FIWARE technologies and concepts.

4. Support SMEs in creating high-impact applications and helping to market their apps cross border in specialised EU markets and beyond.

5. Ensure business value of services/applications for collaborative business networks in food & flower business networks.

Project Consortium

ATB Institut für angewandte Systemtechnik Bremen GmbH; Germany

DLO Stichting Dienst Landbouwkundig Onderzoek; The Netherlands

Euro Pool System International (Deutschland) GmbH; Germany

CentMa GmbH; Germany

iMinds; Belgium

CBHU Campden BRI Magyarország Nonprofit Kft.; Hungary

DCS Fondazione Democenter-Sipe; Italy

EBILTEM Ege University Science and Technology Centre; Turkey

More Information

Harald Sundmaeker (coordinator) e-mail: [email protected]

phone: +49 (421) 22 09 253 mobile: +49 (172) 435 84 53

http://www.FInish-project.eu

ATB Institute for Applied Systems Technology Bremen GmbH Wiener Straße 1; 28359 Bremen; Germany

FInish 24.10.2014


Dissemination Level

PU Public X

PP Restricted to other programme participants (including the Commission Services)

RE Restricted to a group specified by the consortium (including the Commission Services)

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

Change History

Version Notes Date

001 Creation of the document 22.07.2014

002 Refining the overall structure and compiling the initial document structure 25.08.2014

003 Adapting the structure based on the Kick-Off meeting in Bremen 16.09.2014

004 Finalizing draft for contributors 23.09.2014

005 Improving draft, adding links 7.10.2014

006 Finalized draft 10.10.2014

007 Send draft for final revision 24.10.2014

008 Final version 31.10.2014

Document Summary

This document provides insight how organizations can collaborate within the FInish project to develop high-quality and high-impact solutions for food and flower supply chain networks based on FIWARE tech-nologies.

The document is intended to serve as a vehicle to transfer knowledge of the previous phases of the FI-WARE programme to app developers, business architects and users of FI-solutions. Hence, the docu-ment shortly introduces subjects and then refers to relevant background information. The subjects in this document are an introduction of the FInish Project, the Domain: Food and Flower Supply Chains, the organisational context of the FInish project, Future Internet Technologies to build upon, Implementation Examples and finally a guide to support the building of Future Internet Apps.

FInish 24.10.2014


Abbreviations

App Software Application

B2B Business-to-Business

D Deliverable

DoW Description of Work

EC European Commission

e.g. Exempli gratia = for example

EU European Union

EC European Commission

FAQ Frequently Asked Questions

FIA Future Internet Assembly

FI-PPP Future Internet Public Private Partnership

FIWARE Future Internet ware

FP7 Framework Programme 7

GA Grant Agreement

GE Generic Enabler

i.e. id est = that is to say

ICT Information and Communication Technology

IoT Internet of Things

IP Intellectual Property

IPR Intellectual Property Rights

KPI Key Performance Indicator

M Month

MS Milestone

NCP National Contact Point

RTD Research and Technological Development

SE Specific Enabler

SME Small and Medium Sized Enter-prise

ST Sub-Task

T Task

WE Web-Entrepreneur

WP Work Package

FInish 24.10.2014


Table of Contents

1.1 Introduction of FInish ................................................................................................................ 7

1.2 Document Objective and Structure........................................................................................... 7

1.3 The FInish Accelerator at a glance ........................................................................................... 8

2.1 Food and Flower Supply Chains .............................................................................................. 9

2.2 Food Domain-specific challenges for Food and Flower Supply Chains ................................. 10

2.3 Business Process Overview of App User Organisations ....................................................... 12

3.1 A Future Internet Public Private Partnership Programme – FIWARE .................................... 14

3.2 FIWARE .................................................................................................................................. 16

3.3 FIspace ................................................................................................................................... 16

3.4 The FIWARE Accelerator FInish ............................................................................................ 18

4.1 FIWARE Technologies ........................................................................................................... 18

4.2 FIspace platform ..................................................................................................................... 20

4.3 FIspace initial APPs ................................................................................................................ 26

5.1 Fresh Fruit & Vegetables Quality Assurance Trial ................................................................. 29

5.2 Flowers and Plants Supply Chain Monitoring Trial................................................................. 30

5.3 Fish Distribution and (Re-) Planning Trial .............................................................................. 34

5.4 Meat Information Provenance Trial ........................................................................................ 36

5.5 Import and Export of Consumer Goods .................................................................................. 38

5.6 Wrap-up .................................................................................................................................. 39

6.1 Customized User Systems ..................................................................................................... 42

6.2 Guideline for the development of Apps within the FInish project ........................................... 42

FInish 24.10.2014


List of Figures

Figure 1: Smart monitoring and control in perishable supply chains [6] ................................................ 11

Figure 2: Categorisation of the supported business processes ............................................................ 12

Figure 3: Overview of the Phase 1 and Phase 2 FIWARE Projects (http://www.fi-ppp.eu/projects/) ..................................................................................................................... 14

Figure 4: FIspace collaboration platform showing its relationship to domain users and its foundation based on FIWARE generic enablers (GEs) .......................................................... 17

Figure 5: High level conceptual architecture ......................................................................................... 21

Figure 6: Logistics Planning App Overview ........................................................................................... 27

Figure 7 : Principal organization of the FFV food chain. ......................................................................... 29

Figure 8: Relations between the Apps in the Flowers and Plants Trial ................................................. 30

Figure 9: Experiment 1A. Overview of business 2 business logistic inbound interactions .................... 31

Figure 10: Experiment 1B. Overview of business 2 business logistics outbound interactions ................ 31

Figure 11: Overview of the Condition Monitoring App ............................................................................. 32

Figure 12: Overview of the processes modelled in the Expert Quality Assessment App ........................ 32

Figure 13: Overview of processes modelled in the Product Quality Alerts App ...................................... 33

Figure 14: Overview of headlines of processes to be modelled in the Quality Decay Prediction App ......................................................................................................................................... 34

Figure 15: CargoSwApp Process ............................................................................................................ 36

Figure 16: Layout of Import and Export of Consumer Goods Trial .......................................................... 38

List of Tables

Table 1: Overview of Apps developed within the FIspace project (see: www.fispace.eu) ................... 39

Table 2: Steps to develop FInish Apps and the related documentation ............................................... 43

FInish 24.10.2014


1 Introduction

1.1 Introduction of FInish

The FInish project will utilise technologies of the Future Internet Public-Private-Partnership, short FI-WARE, to enable the development and operation of intelligent systems for supply chains of perishable products such as food and flowers. The project includes an ecosystem that brings together: i) business needs of user communities and ii) creative ideas & technological opportunities of software SMEs and web-entrepreneurs. The corner stones of this ecosystem are regional clusters that include close syner-gies with regional developments & policies that are embedded in European networks.

FInish will use enablers from the FIWARE programme, such as FIWARE Generic Enablers (GEs) and the FIspace platform, as a basis to drastically enlarge the number of services/applications available in the FIspace store by involving through open calls SMEs and web-entrepreneurs as developers. As such, the FInish project will enable seamless B2B collaboration and it will empower companies including SMEs and new players to set up and participate in new regional, horizontal and vertical collaboration quickly and at minimal costs. By doing this, FInish wants to give an impulse to the shift from cost-driven to value-based, information-rich supply chains, which will significantly increase the added value, competiveness and sus-tainability of the domain. More specifically, FInish aims to:

1. Empower small and innovative ICT players to develop high-quality and high-impact solutions for food

and flower supply chain networks based on technologies of the FIWARE programme;

2. Develop a large set of innovative and technologically challenging services and applications for virtual-

isation, connectivity and intelligence of food and flower supply chain networks;

3. Implement and validate the technologies and concepts developed in the FIWARE programme;

4. Support SMEs in creating high-impact apps with Future Internet applications and helping to market

their apps cross-border in specialised EU markets and beyond;

5. Ensure business value of services/applications for collaborative business networks in food and flower

industry.

To stimulate the development of high-quality and high-impact solutions the FInish project will make around 4.9 million euro available to SME and web-entrepreneurs. To qualify for this money these SME and web entrepreneurs have to hand in a proposal that describes their solution for this domain, which needs to be based upon FIWARE technologies (e.g. FIWARE GEs and the FIspace Platform). Each pro-posal can receive up to a maximum of 150,000 euro to develop their solution.

1.2 Document Objective and Structure

This document presents a high-level architecture that consolidates previous designs from the FIWARE programme that are related to the management of perishables supply chains. This document can serve as a vehicle to transfer knowledge of the previous phases to the FInish app developers, business archi-tects and end-users. The objectives are twofold:

• To consolidate the agri-food logistics trials of Smart Agri-Food and FIspace and thus to capitalise on the investments and developments concerning the management of perishables supply chains in phase one and two of the FIWARE programme;

• To provide access to information, tools and services of previous FIWARE projects including FIspace and FIWARE GEs to ensure compliance of developments in the other Phase 3 projects.

To do so, the document introduces the organisations and related results of the FIWARE programme and especially the FIspace project. Additionally, it provides references to the relevant information, tools and services of these projects.

Based on this document a Manager should be able to understand the business relevance of the FIWARE programme and the FInish project. A Business Developer should understand the domain if Food and Flower Supply Chains and it specific characteristics, requirements and needs for specific software solu-tions. Business Architects will realize how they can assemble (configure) apps into new solutions. Soft-

FInish 24.10.2014


ware Developers will be provided with technical background and links how solutions, based upon FI-WARE and the FIspace Platform, can be build.

The document is structured as follows. First, it provides an introduction of the domain of Food and Flower Supply Chains, focussing on domain-specific challenges and a functional overview of food and flower supply chain actors. This functional overview can be used to describe what kind of service the application delivers to an end-user organisation. Second, the organisational context is introduced, i.e. the Future Internet PPP programme. At this, special attention is paid to the FIWARE GEs and FIspace project. Third, the document presents a summary of the technical architecture and specifications of FIWARE GEs and the FIspace Platform. Fourth, more details about current applications that are developed within the FIspace project are presented in the example implementations of software solutions. These example implementations are developed within the FIspace Project. The example implementations provide insight into high-quality and high-impact solutions for food and flower supply chains. Fifth and finally, a guideline for app developers is presented about how to develop apps within FInish based on the Future Internet technologies that are introduced in this document.

1.3 The FInish Accelerator at a glance

FInish is one of the 16 accelerator projects in the third phase of the Future Internet Programme.

Acronym: FInish

Full title: Food Intelligence and Information Sharing for Business Collaboration enabled by the Future Internet

Business Domain: Supply Chain of Perishable Food and Flowers; addressing solutions that will help to improve and provide a business value for e.g. growers, traders, processors, manu-facturer, retailers, transport, logistics, service providers in the food and/or flower chain.

Target Audience: SMEs, web-entrepreneurs, start-ups

Project Start: September 1st 2014

Project End: August 31st 2016

Overall Funding: 4.88 Mio Euro for sub-grantees 2 Open Calls for Apps – 1

st Call: 2 Mio Euro and 2

nd Call: 2.48 Mio Euro

250 kEuro for Apps provided by competitions 150 kEuro for awarding the best Apps

Call 1: Open from October, 29th 2014 – December, 10

th 2014

Proposed projects shall generally last 6-12 months Proposed projects shall not exceed the request for a grant larger than 150 kEuro

Call 2: Open from March 2015 – April 2015 (to be detailed) Proposed projects shall generally last 6-12 months Proposed projects shall not exceed the request for a grant larger than 150 kEuro

Competitions: To be defined

Awards: To be defined

Technology: Proposed projects must make use of the FIspace platform (http://fispace.eu) and/ or FIWARE Software (http://catalogue.FIWARE.org/)

FInish 24.10.2014


2 The Domain: Food and Flower Supply Chains

This section is relevant for Business Developers and Business Architects as it describes the domain, food and flower supply chains. This section first provides an overview of such supply chains. Second, the do-main specific challenges are described. Third, an overview is provided describing business functions of application user organisations. This functional overview can be used to describe what kind of service the application delivers to an end-user organisation.

2.1 Food and Flower Supply Chains

The supply of fresh food products is of vital importance to feed Europe in a healthy way, while Europe has also an important role in feeding the world. The sector has a strong competitive position, for example: the EU is the world’s largest food and drink exporter with a share of EU exports to world markets of 16.1% in 2011

1.

At the same time, food products and other perishables such as flowers impose very challenging demands on the management of its supply chains [3]. Due to the high perishability, quality conditions including temperature has to be controlled from farm to fork, order-to-delivery lead-times are very short (while vol-umes are high) and supply chains have to deal with unpredictable variations in quality and quantity of supply. Consequently, planning and control systems need to be very flexible, enabling last minutes changes and re-allocations, but also proactively enabling early warning and preventive control. Further-more, in the past years numerous food calamities have required massive product recalls, e.g. the E. coli outbreak and the horse meat scandal. As a result there is a clear need for high-speed, high precision methods for product recalls and highly transparent product tracing approaches.

On top of these challenges, supply chains of perishable products are currently facing high-impact trends.

• Sustainable supply chains are becoming ‘license to deliver’: currently about 20% - 50% of food is wasted during its journey to the consumer and food products accounts for an important part of the emissions produced by the transportation sector . The society does no longer accept the ex-tremely high waste of food and the big CO2 footprint of food products. As a result, there are a lot of initiatives to reduce the environmental impact of perishable supply chains, e.g. Green Logis-tics, Cradle-to-Cradle, etc.

• Increasing interest in ‘local’ as opposed to the dominance of ‘global’: food has always been a means for consumers to profile themselves in a social environment, but in the last decade food culture has clearly grown in importance. Sustainability aspects are much discussed, by chefs as well as large segments of consumers and NGOs.

• Growing attention for impact of food on health: consumers and society are increasingly aware that there is a strong relation between food consumption and so-called diseases of civilization, in-cluding obesity and food allergies.

• Breakthrough of eCommerce in perishable products: the positive experiences in web-shops of non-perishables are now also transferred to fresh products. Citizens in e.g. Brussels buy orang-es, ham and olive oil from Spain and have it delivered fresh in a few days. Retailers and special-ised internet traders are trying to achieve competitive advantage with the delivery of high-quality fresh products. To do so, new solutions for fulfilment and last-mile deliveries of perishables are introduced (for example: Amazon Fresh).

• Open innovation: innovation processes in the food industry are increasingly characterized by co-operation and by a greater user involvement. Open innovation approaches such as Living Labs (LL) are increasingly popular and user communities are often co-creators of product and service innovations.

In order to cope with the trends mentioned above and intensified by the economic crisis, the way of doing business in perishable supply chains is currently being transformed. Companies are changing towards new levels of cooperation to add more value for the end customers. Also new players are becoming ac-tive that introduce new business concepts and innovative services. These changes have a huge impact on perishable supply chains, which are becoming highly dynamic and heterogeneous networks, demand-ing for intensive information exchange. When conducting business in such highly networked, often bor-

1 A supply chain is a connected series of business processes performed by a network of interdependent

organizations working together to control, manage and improve the flow of materials and information from suppliers to ultimate consumers (adapted from [1, 2])

FInish 24.10.2014


der-crossing, dynamic and competitive environments, it becomes crucial for the involved actors to collab-orate in an efficient, effective and trustworthy manner. To do so, demand and supply information has to be exchanged and communicated in a timely, secure and flexible way to a variable network of down-stream and upstream partners. Supply chain actors including SMEs have to be able to connect quickly and at minimal costs (‘pick, plug and play’). Consequently, affordable solutions are necessary which can be utilised by SMEs that lack significant resources and specialised competences.

2.2 Food Domain-specific challenges for Food and Flower Supply Chains

A basic motivation of FInish is to support the realisation of software applications that are promoting a shift from cost-driven to value-based, information-rich supply chains, which will significantly increase the add-ed value, competiveness and sustainability of the domain. From a strategic perspective, applications that are promising tangible benefits and a sustainable value for the overall society with respect to the following dimensions are prioritised:

• Reduce the environmental impact of perishable supply chains,

• Increase interest in ‘local’/regional as opposed to the dominance of ‘global’ food,

• Promote the awareness with respect to health & related risks,

• Empower small & innovative ICT players to develop high-quality and high-impact solutions for food and flower supply chain networks and

• Facilitate breakthrough of e-commerce in perishable products for SME type agri-food chain ac-tors.

From a technical and business process perspective, FInish is aiming at supporting the realisation of new solutions that will specifically facilitate the collaboration in the agri-food chain. To name a few, this could address the following measures, but is open to additional ideas:

• Improve business to business collaboration and data exchange in combination with added value functionalities that support agri-food companies in their daily business,

• Provide a better transparency regarding products and processes,

• Open new and informed ways of conducting business within food supply networks,

• Integrate networked devices (IoT) and make use of mobile concepts.

FInish will make it possible for companies in different perishable industries to flexibly configure supply chain management systems from the business apps that will be developed in this project. The apps will be available in the FIspace store and can, together with other FIspace apps, be used to rapidly implement customised solutions. The business apps will provide innovative and technological challenging services and applications with a high business impact in food supply chain networks. The functionalities of the apps to be developed will range from new information sharing capabilities to advanced intelligence capa-bilities based on that information. Based on the insights in Smart Agri-Food and FIspace [4, 5] , three key functional areas of these apps distinguished (See Figure 1):

• Food Intelligence

• Food Web Connectivity

• Real Time Virtualization

In the following sections the different functional areas are described in more detail.

FInish 24.10.2014


Figure 1: Smart monitoring and control in perishable supply chains [6]

2.2.1 Real Time Virtualisation

One of the main FI challenges for logistics is to enable the agri-food industry to deal with high dynamics and uncertainty in supply and demand. It is widely accepted that virtualized networks are an important answer to challenges posed by the markets and the opportunities offered by nowadays affordable new technologies (in particular ICT, Sensors, Automatic Identification and Mobility technologies (including RFID), conditioning, transport, etc.). Virtual logistics networks are information-based rather than invento-ry-based. Consequently, information systems are important enablers of virtual networks. However, the dynamic nature of virtual networks imposes stringent demands on the enabling information systems. They should facilitate the dynamic construction of temporal supply chains and the real-time and network-wide transparency of the products and resources that are needed to achieve its value proposition. Therefore, reliable information must be shared timely throughout the supply chain.

With real-time virtualization the physical flows of products and logistics resources (objects) is decoupled from the information flows for planning, control and coordination/orchestration. The geographically dis-persed physical objects continuously update a virtual representation of the object following the concept of Intelligent Cargo, i.e. (lots of) agri-food products and logistic resources. This is done by logging their iden-tity, location and state, and communicates this object-information real-time via the internet (the Internet of Things, IoT). They also can receive information and perform corrective and preventive actions on the physical object (smart objects). Enabling technologies include real-time logging, sensor and actuator net-works and RFID.

In FInish apps should be developed that leverage the FIspace platform and the underlying GEs (especial-ly the IoT services enablers). The apps in this category must add specific services and applications for perishable supply chain networks. Examples are applications for advanced visioning (including high-speed/low-cost solutions, 3D, and internal features such as ripeness), for quality inspection of food and flowers based on (mobile) augmented reality, etc.

2.2.2 Food web Connectivity

Food web connectivity is the timely, error free exchange and secure communication of information in highly dynamic supply chain networks to enable adequate response based on up-to-date and reliable virtual representations. This in particular requires solid infrastructures to communicate information of ob-jects while they are transported and standards for a seamless identification and exchange of prod-uct/logistics data . It also imposes stringent requirements on the interoperability of the underlying enter-prise information systems. Enabling technologies include SOA, data exchange standards, trust/identity capabilities, as well as cloud computing. Several of these aspects are related to the Internet of Services (IoS).

A complicating factor in the food and flower industry is that the properties of agri-food products are highly dynamic because they are living products, which imposes stringent requirements on the timeliness of data exchange. Apps developed within in FInish can be based on the functionalities provided by the FIspace platform (e.g. the Business Collaboration Core, the System & Data Integration module and the Security, Privacy, and Trust Management module) and the underlying GEs (including Cloud Hosting and

FInish 24.10.2014


Security enablers). However, in FInish also specific apps for the food industry can be developed. Exam-ples are applications for exchange of sector-specific master data (in particular product information), map-ping services for sector-specific standards (e.g. concerning food safety regulation and sustainability la-bels).

2.2.3 Food Intelligence

Food Intelligence is the usage of the virtualization data for intelligent decision support. FInish aims to fund apps that provide functionalities for different levels of intelligence, including interaction, monitoring, prob-lem notification, deviation management, planning and optimisation. The apps in this category will add specific services and applications for perishable supply chain networks. They should utilise generic ser-vices of the FIspace platform and the underlying GEs, especially the enablers for Complex Event Pro-cessing and Data / Context Management. Examples of food-specific intelligence functionalities are apps for early warning in case of food incidents or unexpected quality deviations (e.g. temperature or humidity changes), advanced forecasting about consequences of detected changes by the time the product reach-es destination, e.g. dynamic simulation of best-before dates.

2.3 Business Process Overview of App User Organisations

Besides the classification into the functional areas real-time virtualization, foodweb connectivity and food intelligence, apps can also be categorised based on the supported business processes. Such categorisa-tion is important to define the scope of the domain, to clarify how different apps are interrelated and to identify relevant related standards.

The supported business processes can be categorised in functional groups and cross-functional manage-rial processes, as follows (see Figure 2).

Figure 2: Categorisation of the supported business processes

The functional groups are Source, Transport, Deliver and Sell.

The Source function comprises all business processes that are related to the procurement of goods and services to meet planned or actual demand and the inbound logistics. Examples are: supplier selection, purchase order entry, products receipt, quality inspection of incoming products, product transfer to the warehouse, storage, payment of purchase invoices, etc.

FInish 24.10.2014


The Transport function comprises all business processes that are related to move products between sup-ply chain stakeholders via different modes of transportation (i.e. road, rail, air and water freight). Exam-ples are: carrier selection, transport order processing, routing of shipments, (un)loading, shipping, import / export inspection (including customs and phytosanitory/veterinary inspections), etc.

The Deliver function comprises all business processes that are related to prepare products for delivery and meeting customer customer’s delivery requirements. Examples are: order receipt, picking, quality inspection of outgoing products, packing, lab testing, billing, replenishment, Returnable Trade Item (RTI) handling and waste disposal.

The Sell function comprises all business processes that are related to the establishment and conclusion of transactions between supply chain actors, in particular, sales and purchasing. Examples are: providing supply information, demand forecasting, bidding, negotiation, contract management and customer rela-tions management.

The cross-functional managerial processes are concerned with the planning, control and coordination structures that facilitate the instantiation and execution of processes in a supply chain context. The follow-ing managerial processes are defined: Plan, Monitor, Interact, Manage Deviations and Optimise.

FInish 24.10.2014


3 Organisational context

This section describes the outline of the European Future Internet Public Private Partnership (FIWARE) Programme. In this section an overview of the FIWARE programme and it projects is provided. We elabo-rate on the projects that are relevant for the FInish Project.

3.1 A Future Internet Public Private Partnership Programme – FIWARE

The FIWARE Programme is a European initiative for Internet-enabled innovation. The FIWARE pro-gramme will accelerate the development and adoption of Future Internet technologies in Europe, advance the European market for smart infrastructures, and increase the effectiveness of business processes through the Internet.

The FIWARE programme covers a wide scope of usage areas through a set of use case projects that make use of the FIWARE technologies. These technologies are used for setting-up trials of advanced Future-Internet-based services and applications. In Figure 3 an overview of the FIWARE Phase 1 and Phase 2 projects is provided.

Figure 3: Overview of the Phase 1 and Phase 2 FIWARE Projects (http://www.fi-ppp.eu/projects/)

In this program there are different types of projects. Below a list of these projects are provided.

TECHNOLOGY FOUNDATION

The goal of the technology foundation is to advance the global competitiveness of the EU economy by introducing an innovative infrastructure for cost-effective creation and delivery of services, providing high QoS and security guarantees. The link to the FIWARE program is:

• FIWARE (http://www.FIWARE.org/)

USAGE AREAS AND USE CASE PROJECTS

The FIWARE programme is covering a wide scope of usage areas through a set of use case projects that make use of the FIWARE GEs. The FIWARE Programme phase 1 included 8 use cases projects, and the ongoing phase 2 includes 5 use case projects which will lead to SME-driven use case implementations in phase 3. The phase 1 and 2 projects for each domain are:

TRANSPORT, LOGISTICS AND AGRI-FOOD

• FINEST (Phase 1) (http://www.finest-ppp.eu/)

• SmartAgriFood (Phase 1) (http://www.smartagrifood.eu/)

• FIspace (Phase 2) (http://www.fispace.eu/)

PERSONAL MOBILITY

FInish 24.10.2014


• Instant Mobility (Phase 1) (http://instant-mobility.com/)

SOCIAL CONNECTED TV, MOBILE CITY SERVICES, AND VIDEO GAMES

• FI-CONTENT (Phase 1) (http://www.ficontent.eu/)

• FI-CONTENT 2 (Phase 2) (http://www.ficontent.eu/)

SMART CITIES AND PUBLIC SECURITY

• SafeCity (Phase 1) (http://www.safecity-project.eu/)

• OUTSMART (Phase 1) (http://www.fi-ppp-outsmart.eu/)

SMART ENERGY

• FINSENY (Phase 1) (http://www.fi-ppp-finseny.eu/)

• FINESCE (Phase 2) (http://www.finesce.eu/)

ENVIRONMENT

• ENVIROFI (Phase 1) (http://www.envirofi.eu/)

MANUFACTURING

• FITMAN (Phase 2) (http://www.fitman-fi.eu/)

E-HEALTH

• FI-STAR (Phase 2) (http://www.fi-star.eu/)

ACCELERATOR PROJECTS (PHASE 3)

• CEED Tech (Smart cities, Energy & Environment, Media & Content, Manufacturing & Logistics)

• CreatiFI (Media & Content)

• EuropeanPioneers (Smart cities, Media & Content, Social & Learning)

• FABulous (Media & Content, Manufacturing & Logistics)

• FI-ADOPT (eHealth, Social & Learning)

• FI-C3 (Smart cities, eHealth, Media & Content)

• FICHe (eHealth)

• Finish (Transport, Agrifood, Media & Content)

• FINODEX (eHealth, Transport, Energy & Environment)

• FRACTALS (Agrifood)

• Frontier Cities (Transport)

• IMPACT (Smart cities, Media & Content, Social & Learning)

• INCENSe (Smart cities, Energy & Environment)

• SmartAgriFood2 (Agrifood)

• SOUL-FI (Smart cities, Transport, Energy & Environment, Social & Learning)

• SpeedUp (Smart cities, Energy & Environment, Agrifood)

More information about the other Accelerator Projects can be found on: http://www.fi-ware.org/fiware-accelerator-programme/

PROGRAMME FACILITATION AND SUPPORT FOR PHASE 1, 2 AND 3

• CONCORD

• FI Business

• FI-IMPACT

• FI-LINKS

FInish 24.10.2014


The FIWARE programme is setting up a technology foundation. The FIWARE GEs developed in this pro-gramme are used within the FIspace Platform. In the remainder of this document we will elaborate on FIWARE and FIspace because the components and platform of these projects need to be used in apps that are developed within the FInish Project.

For more information see: www.fiware.org

3.2 FIWARE

FIWARE is an innovative, open cloud-based infrastructure for cost-effective creation and delivery of Fu-ture Internet applications and services. FIWARE API specifications are public and royalty-free, driven by the development of an open source reference implementation which accelerates the availability of com-mercial products and services based on FIWARE technologies.

The goal of the FIWARE project is to advance the global competitiveness of the EU economy by introduc-ing an innovative infrastructure for cost-effective creation and delivery of services, providing high QoS and security guarantees. FIWARE is designed to meet the demands of key market stakeholders across many different sectors, e.g., healthcare, telecommunications, and environmental services. FIWARE unites major European industrial actors. The key deliverables of FIWARE will be an open architecture and a reference implementation of a novel service infrastructure, building upon generic and reusable building blocks developed in earlier research projects. Additionally it will demonstrate how this infrastructure sup-ports emerging Future Internet (FI) services in multiple Usage Areas, and will exhibit significant and quan-tifiable improvements in the productivity, reliability and cost of service development and delivery – build-ing a true foundation for the Future Internet.

From an architectural perspective, FIWARE is based on the following main foundations:

• Service Delivery Framework – the infrastructure to create, publish, manage and consume FI ser-vices across their life cycle, addressing all technical and business aspects.

• Cloud Hosting – the fundamental layer which provides the computation, storage and network re-sources, upon which services are provisioned and managed.

• Support Services – the facilities for effective accessing, processing, and analyzing massive streams of data, and semantically classifying them into valuable knowledge.

• IoT Enablement – the bridge whereby FI services interface and leverage the ubiquity of hetero-geneous, resource-constrained devices in the Internet of Things.

• Interface to Networks – open interfaces to networks and devices, providing the connectivity needs of services delivered across the platform.

• Security – the mechanisms which ensure that the delivery and usage of services is trustworthy and meets security and privacy requirements.

The FIWARE project has delivered multiple Open-Source GEs that can be reused by software companies to develop new solutions faster and better. In the Technical specification of FIWARE (Section 4.1) more details about these GEs are presented.

For more information see: http://www.FIWARE.org

3.3 FIspace

FIspace is a FIWARE phase 2 project which objective is to drive the development of an integrated and extensible collaboration service together with an initial set of domain applications, thereby establishing the standard for supporting and optimizing inter-organizational business collaboration in global transport, logistics, and agri-food business.

These objectives will be achieved through leveraging and capitalizing on the outcomes of two successful Phase I use case projects – FInest and SmartAgriFood –, as well as by utilizing the GEs (software) avail-able from the FIWARE programme. Achievement of these objectives is partly demonstrated through trial experimentation in the domains of agri-food and transport and logistics businesses that comprise diverse trial sites, usage scenarios, and stakeholders. These Implementation Examples can be found in Section 05.

FIspace develops a multi-domain collaboration and integration service, based on FIWARE technologies, enabling new business collaboration opportunities between actors in a supply chain and software service providers.

FInish 24.10.2014


A high level schematic of the FIspace collaboration platform showing its relationship to domain users and its foundation based on FIWARE GEs is shown in Figure 4.

Figure 4: FIspace collaboration platform showing its relationship to domain users and its foundation based on FIWARE generic enablers (GEs)

The central features of the FIspace collaboration service will be:

• Provisioning of the FIspace service will follow the Software-as-a-Service delivery model, which means that FIspace services can be accessed anywhere at any time via any device;

• The FIspace service is an open service that can be extended and customized for specific stake-holder demands by integrating domain apps (similar to the iPhone and Android business models);

• A domain app store facilities the marketing of targeted applications that take advantage of the collaboration and mash up services of the FIspace and its underlying FIWARE GEs;

• A collaboration manager for business-to-business networks that supports the planning and exe-cution of business operations from a global perspective with message-based coordination among the involved business partners;

• Integrated techniques for monitoring and tracking on the basis of data integration from the Inter-net of Things, including sensor systems and smart item technologies accessible via FIWARE GEs;

• Information integration from legacy and third party systems enabled through a service-based in-tegration layer that is enabled and supported by FIWARE GEs;

• Role-based views for the individual participants in the business networks along with integrated security and privacy management for fine-grained access control to confidential information

The exploitation of the FIspace Platform is currently in progress. There will become multiple FIspace in-stances available that focus on different business communities to offer their integration services to. The FIspace Platform will be managed by a foundation.

For more information see: http://www.fispace.eu/ or http://www.fispace.eu/Documentations/Deliverables/FIspace-D500.7.1%20Detailed%20plan%20to%20move%20into%20phase%203.pdf

FInish 24.10.2014


3.4 The FIWARE Accelerator FInish

FInish is a FIWARE phase 3 accelerator project which will publish Open Calls for the distribution of grants to small and medium sized enterprises, web-entrepreneurs as well as start-ups. The organisations receiv-ing grants by the FInish project are required to use the FIWARE and/or FIspace platforms to develop ICT solutions (apps) that can be used in Food and Flower Supply Chains.

To stimulate the development of these ICT solutions the FInish project will make around 4.9 million euro available to SME and web-entrepreneurs. To qualify for this money these SME and web entrepreneurs have to hand in a proposal that describes their solution, which needs to be based upon FI technologies made available by FIWARE and FIspace. Each proposal can receive up to a maximum of 150,000 euro to develop their solution.

The apps that are funded by FInish are required to use FIWARE components or need to extend the func-tionality of the FIspace Platform. This extendibility of the FIspace Platform is achieved by means of two key mechanisms:

• Addition of functionality through Apps. The Apps will provide value added services and wrapped software capabilities. This means that new apps can be developed (for which FIWARE GEs must be used). Such Apps could offer features such as planning support, pricing proposals, exception reporting and decision support, shipment status, meat transparency information, or augmented reality product information.

• Configuration through collaborative workflows: FIspace allows Apps to be composed along col-laborative workflows and mashed-up into personalized dashboards for users. In addition, FIspace can be configured to allow flexible integration of data sources of users and linking those data sources to Apps along collaborative work-flows. As an example, one could envision that a meat transparency information App is composed with an augmented reality product information App through a collaborative workflow involving meat producers, shippers and retailers.

Small and medium sized enterprises, web-entrepreneurs as well as start-ups could receive grants for developing new Apps offering new functionality or develop a new App and compose this new app with other existing Apps to offer new functionality to end-users. All Apps funded by FInish need to utilize the FI technologies (FIWARE GE’s and/or FIspace) and have end-users that are part of Food and Flower supply chains.

For more information see: http://www.finish-project.eu/

4 Future Internet Technologies to build upon

Within the FInish project Small and medium sized enterprises, web-entrepreneurs as well as start-ups could receive grants for the development of new applications. These application need to be based upon the software developed within the FIWARE programme.

4.1 FIWARE Technologies

4.1.1 FIWARE

FIWARE provides enhanced OpenStack-based cloud hosting capabilities plus a rich library of compo-nents offering a number of added-value functions offered “as a Service”. These components, called Ge-neric Enablers (GEs), provide open standard APIs that make it easier to connect to the Internet of Things, process data and media in real-time at large scale, perform BigData analysis or incorporate advanced features to interaction with the user.

Availability of open source Generic Enabler implementations (GEs) will accelerate availability of multiple commercial FIWARE providers, all supporting the same set of APIs. As a result, FIWARE becomes an open alternative to existing proprietary Internet platforms. Therefore organisations can decide themselves who will operate the environment where their application and, even more important, their data will be hosted.

For more information see: http://www.FIWARE.org/

FInish 24.10.2014


4.1.2 Generic Enablers

The FIWARE project has currently different Generic Enabler available related to different chapters.

The available chapters are:

• Advanced Middelware and Web User Interfaces

• Applications/Services Ecosystem and Delivery Framework

• Cloud Hosting

• Data/Context Management

• Interface to Networks and Devices

• Internet of Things Service Enablement

• Security

For each of these chapters often multiple generic enables are available.

For more information see: http://catalogue.FIWARE.org/enablers?chapter_tid=All

4.1.3 FIWARE lab

In the FIWARE Lab a working instance of FIWARE GEs are available for experimentation. It can be used to setup the basic virtual infrastructure needed to run applications that make use of the APIs provided by FIWARE GEs deployed as a Service.

See: http://lab.FIWARE.org/

4.1.4 FIWARE Courses

FIWARE offers an eLearning platform, where you can find training courses, lessons and many other con-tents regarding FIWARE technology.

These courses are divided into different categories. A list of these courses and their categories can be found below.

FIWARE Lab

• Applications and Services Ecosystem and Delivery Framework

• Business Framework (Store, RSS and Business Modeler)

• Application Mashup (Wirecloud)

• Repository RI - SoPeCo Performance Test

• Marketplace RI - Pricing Engine Extension - Simulation-based Pricing Decision Support

• Apps and Services Overview

Cloud Hosting

• Software Deployment and Configuration (Sagitta)

• PaaS Manager (Pegasus)

• Data Center Resource Management (DCRM)

• How to create chef recipes for FIWARE GEs

• Data/Context Management

• Complex Event Processing (IBM Proactive Technology Online) Summary

• Big Data Analysis (Cosmos)

• Publish/Subscribe Broker (Orion Context Broker)

• Stream Oriented (Kurento)

Interface to Networks and Devices

• Openflow Network Interface and Control (OFNIC)

• Internet of Things (IoT) Services Enablement

• Protocol Adapter (MR CoAP)

• IoT Template Handler GE

• Backend Configuration Manager (IoT Discovery)

• NEC IoT Broker introductory course

• Gateway Data Handling (EspR4fastData)

FInish 24.10.2014


Security

• Security Monitoring (Scored Attack Paths)

• Security Monitoring (MulVAL Attack Path Engine Web Application)

• Security Monitoring (Remediation)

• Identity Management (KeyRock)

• Self enrolment Access Control (OAUTH-API-AZ)

• How to authenticate your users in your apps using FIWARE Account

Advanced Middleware and Web-based User Interface

• 2D-UI

• Cloud Rendering

• Interface Designer

• Geographical Information System Data Provider

• Real Virtual Interaction GEi

Development Tools

• UFT Framework

• Fusion Forge Project & User Management

• FI Application Project Management

• Software Performance Cockpit

• FusionForge Connector

• PROSA: An Online Monitoring and Testing Tool

• REST Client Generator

• Trace Analyzer

• NGSI TestServer

FIWARE Ops

• FI-Ops Core Concepts

These courses can be found on: http://edu.FIWARE.org/

4.2 FIspace platform

The FIspace platform will be a Future-Internet-based extensible SaaS-platform that enables seamless, efficient, and effective business collaboration across organizational boundaries. This FIspace Platform will facilitate the establishment of ecosystems with business benefits for both stakeholders from industrial sectors as well as the ICT industry.

The FIspace platform builds on top of a selection of GEs and adds a layer of abstraction that hides under-lying details. Currently, FIspace tests, makes use or plans to make use of the following GEs from the following chapters:

• Data Chapter: Complex Event Processing, Publish/Subscribe Broker

• Apps Chapter: Service Description Repository, Service Registry, Marketplace, Store, Revenue Sharing, Application Mashup, Mediator

• IoT Chapter: (Backend) Configuration Management, (Backend) IoT Broker, (Backend) Device Management, (Gateway) Data Handling, (Gateway) Device Management

• Security Chapter: Security Monitoring, Identity Management, Privacy, Access Control, Data Handling, Context-based Security & Compliance, Malware Detection Service, Content-based Se-curity

• I2ND Chapter: Connected Device Interfacing, Network Information and Control, Service Connec-tivity Capability and Control

• MiWi Chapter: Advanced Middleware

More information, see: the FIspace website (http://www.fispace.eu/) and the Wiki (http://dev.fispace.eu/doc/wiki/Home ).

http://www.fispace.eu/

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

FInish 24.10.2014


4.2.1 FIspace Architecture

FIspace provides a multi-domain cloud-based platform, following the Software-as-a-Service delivery model, that will enable the seamless, efficient, and effective business collaboration across organizational boundaries and that will facilitate the establishment of business ecosystems with business benefits for both stakeholders from industrial sectors as well as the ICT industry. As an open platform it can be ex-tended and customized by integrating (domain-specific or more generic) Apps. These Apps will be pro-vided via an App store and can be integrated with and reused by other Apps.

It should be noted that different from typical smartphone Apps, FIspace Apps will not be built towards a given (and possibly fixed) programming interface (API) [7]. Rather, one key aspect of FIspace Apps is that they will declare what input data or events they require. In this regards, the FIspace App model is much closer to the software (Web) service or the component based software-engineering model, where reusable features are offered through interfaces defined by the services/components, and interested par-ties can select and combine and mash-up those services/components into more complex service compo-sitions, cf. [8].

The core of the FIspace platform is a business collaboration ‘engine’ that supports the planning and exe-cution of business operations. It also includes integrated techniques for monitoring and tracking on the basis of data integration from the IoT (for example sensor systems) as well as from legacy- and third-party systems. This is realized through a service-based integration layer building upon FIWARE GEs (cf. below). The platform accommodates role-based views for individual actors in the business networks, and integrated security and privacy management for access control to confidential information.

The FIspace platform constitutes seven major building blocks (called modules) as illustrated in Figure 5. Each of those modules provides dedicated capabilities.

Figure 5: High level conceptual architecture

Core Layers / Tiers: The FIspace platform core consists of the following three major tiers (or layers):

• User Front-End: The User Front-End serves as the main point of access for users of the plat-form services and Apps, and constitutes a configurable and graphical user interface (for more de-tails see 4.2.1.1).

• B2B Collaboration Core: 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, man-agement, execution, and monitoring of collaborative workflows (business processes) in the FIspace platform (for more details see 4.2.1.2).

• System & Data Integration: The System and Data Integration Layer allows for the integration of existing legacy and business systems as well as the integration of external systems and services. It includes facilities for data mediation (for more details see 4.2.1.3).

Furthermore, the platform contains the following 5 building blocks:

FInish 24.10.2014


App Store: The App Store provides the tool-supported infrastructure for providing, finding, and purchas-ing FIspace Apps, which provide re-usable IT-solutions supporting business collaboration scenarios and which can be used and combined for the individual needs of users (for more details see 4.2.1.4).

Security, Privacy and Trust Framework: The Security, Privacy & Trust framework provides secure and reliable access and, where needed, exchange of confidential business information and transactions using secure authentication and authorization methods that meet required levels of security assurance. Authen-tication, authorization and accounting technologies will provide user management & access control fea-tures (for more details see 4.2.1.5).

Software Development Toolkit: The SDK provides tool-support for the development of FIspace Apps. The SDK will ease the work of App developers during the implementation of the Apps, providing specific tools and libraries that hide the more complex aspects of the platform (for more details see 4.2.1.6).

Operating Environment: The Operating Environment ensures the technical interoperability and commu-nication of (possibly distributed) FIspace components and FIspace Apps and the consistent behaviour of FIspace as a whole. Its main feature is the Cloud Service Bus (CSB) providing event bus and pub/sub capabilities (for more details see 4.2.1.7).

The following sections will further introduce these modules.

Online documentation for the FIspace Architecture: FIspace Deliverable D200.2 (http://www.fispace.eu/Documentations/Deliverables/FIspace-D200.2%20Technical%20Architecture%20and%20Specification.pdf)

4.2.1.1 User Front-End

The User Front-End serves as the main point of access for users of the platform services and Apps. It includes the following main features:

• Customizable user dashboards: To ensure our applications are usable, the front-end strives to provide an environment where they feel comfortable, i.e., provide interaction patterns that under-stand limitations and offer potential opportunities to the users;

• Social networking and collaboration features for business partners;

• Access from anywhere across multiple devices.

The User Front-End builds the main access point for users of the FIspace platform. Through the integra-tion of external widgets, 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 specific needs, tasks and roles. Beyond the adaptation to different devices, the User 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 companies. The Front-End also enables users to create relations to business partners to facilitate the communication among them (com-parable to modern social networks).

Online documentation for User Front-End: http://dev.fispace.eu/doc/wiki/Home

4.2.1.2 B2B Core

At the heart of the envisaged FIspace platform reside the Business-to-Business 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 busi-ness processes in the FIspace platform. The B2B Core consists of two interrelated components:

• 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. 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, i.e., situations that require appropriate reactions;

• Authoring tools: Both engines will be accompanied by respective authoring tools that allow de-fining business entities resp. event rules.

FInish 24.10.2014


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. This approach relies on the notion of entities (aka, as business entities, artefacts, or dynamic artefacts, or business collaboration objects). These provide 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 will use the GSM (Guards, Stages, and Milestones) model to specify the lifecycle schema of the business entities.

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. Examples of situations of interest can be: Missing documentation at a certain point in time, a sensor reading outside a permitted range, 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 ex-ternal systems or sensors).

The EPM in FIspace supports two types of situation detection capabilities: reactive and proactive. Reac-tive rules analyse past events and derive situations by applying pattern matching over a single or a set of events over time. Proactive rules, on the other hand, relate to situations that are likely to happen in the (near) future. In general, we refer to proactive event-driven computing as the ability to mitigate or elimi-nate undesired states, or capitalize on predicted opportunities—in advance. This is accomplished through the online forecasting of future events, the analysis of events coming from many sources, and the appli-cation of online decision-making processes.

Online documentation for B2B Collaboration Core: http://dev.fispace.eu/doc/wiki/Home

4.2.1.3 System & Data Integration

The System and Data Integration Layer allows for the integration and continued usage of existing legacy and business systems as well as the integration of external systems and services, including support for:

Connecting business and legacy systems used by individual users by means of Tool-supported mechanisms, supporting the creation of “connectors” (using common interface standards such as EDI) to business and legacy systems;

Connecting external services (e.g., IoT or 3rd

party services) by means of APIs for importing / exporting data (such as REST or SOAP);

Handling heterogeneous data by means of mechanisms for data mediation;

The overarching purpose of System and Data Integration is to provide a robust and scalable infrastructure that enables seamless integration of external legacy systems/IoT systems with the FIspace platform and applications deployed on it. Outputs from the task will facilitate the implementation of Web based, FIspace-driven applications by providing unifying data models, data mediation tools and system integra-tion APIs.

Online documentation for System & Data Integration: http://dev.fispace.eu/doc/wiki/Home

4.2.1.4 App Store

The App Store provides the infrastructure for providing, finding, and purchasing FIspace Apps, which provide re-usable IT-solutions supporting business collaborations and can be used and combined for the individual needs of users; the FIspace Store includes:

The software infrastructure to support the provisioning, discovery, purchase, and use of FIspace Apps, including a registry of Apps;

Facilities for financial management of the FIspace Apps (pricing, payment, revenue sharing).

FInish 24.10.2014


The FIspace Store is concerned with the software infrastructure to allow for the provisioning and con-sumptions of FIspace Apps, therewith providing the core elements for the monetization throughout the ecosystem that shall be facilitated by FIspace. All FIspace Apps shall be made available in the Store and consumer will be supported with easy to use search and consumption features. The consumption in-cludes the purchase support as well as deployment and runtime support. Features for the former contain an App purchase processes. Features for the latter include capabilities for dynamically connecting the Apps (which may run on different servers) to the Cloud Service Bus of the FIspace platform. Finally, for App customers are informed about the mandatory and optional rights the App requires (before purchase) and enables him or her to configure those for each App (after purchase). For App developers, publication support is provided together with an integrated compliance check for publishing new Apps in a simple way in the FIspace store. An important part of the App Store will be also the application's lifecycle sup-port, including bug fixes and upgrades and connection with the users that purchased the App.

Finally, Financial management is part of the FIspace Store which enables App providers to run statistics and share revenue with involved partners (e.g., developer of re-used component) using different revenue models.

Online documentation for FIspace Store: http://dev.fispace.eu/doc/wiki/Home

4.2.1.5 Security, Privacy & Trust (SPT) Framework

The aim of the Security, Privacy & Trust framework of the FIspace platform is to provide secure and relia-ble access and, where needed, exchange of confidential business information and transactions using secure authentication and authorization methods that meet required levels of security assurance. Authen-tication, authorization and accounting technologies will provide user management & access control fea-tures.

The main features of the SPT framework have been driven by an initial analysis of the SPT functionalities that will be required by industrial actors that will be users of the FIspace platform, and industrial technolo-gy suppliers who will exploit the FIspace platform to provide Apps and associated services to the industri-al actors. The main feature categories that have been considered in the design of the SPT framework for FIspace are:

Identity and Trust: Current situation is that often two business actors establish identity and trust to ex-change information based on some previous knowledge of one another, having been in physical commu-nication. In more advanced and eventually more common scenarios, actors will not be able to rely on having physical contact with other FIspace actors, and strategies such as exploiting online profiles, repu-tation (ranking), certification or registration data bases, etc. will be supported.

Access Control: This will include features in order to validate a user’s identify and thus only allow indi-viduals and organizations that are authorized to connect and that they can only access the information and data they are allowed to access.

Authentication: This will include facilities for authenticating individual users, third-party systems, net-worked resources, and it will need to go down to fine-grained events, and data objects to ensure that only authentic entities are allowed to connect and communicate with the FIspace platform.

Data Security: Those mechanisms will ensure that data is being encrypted and does not leave the FIspace premises unencrypted, as well as that data can only be accessed by users with the respective credentials;

Security Assurance: FIspace will provide strong security assurance that commercial information and transactions are secure, can be trusted and are not vulnerable to malicious actions. FIspace will use a compositional security assurance and accounting process, separating concerns where possible. In a component based design process, independently developed components are assessed and matched to specific system security requirements to determine if they meet the system security objectives. For inde-pendently developed components such as Apps it is possible to provide assurance provided we can verify an App adheres to a set of system-wide and App-specific security policies. As the cost of full verification of independent Apps is costly and time consuming, FIspace complements the verification of security poli-cy adherence by Apps with monitoring mechanisms to detect and prevent unacceptable or unexpected App behaviour;

Developer support to ensure correct usage of necessary security mechanisms in FIspace: SPT patterns and guidelines underlie the Development Toolkit (see Section 4.2.1.5) to ensure that SPT issues are con-sidered by App developers.

FInish 24.10.2014


Concerning privacy and data ownership, one important design consideration that should be mentioned is that operational and business data per se is typically not stored persistently in the FIspace platform (i.e., in the Cloud). Rather data resides with the data owner (and on its premises) but FIspace will provide ac-cess to this data (programmatic and access rights) to the entities that require to get access to this data. Typically, only “meta-data” such as events about actual data objects that have changed (change event) will be stored and managed by the platform, as well as user registration information.

Online documentation for SPT Framework: http://dev.fispace.eu/doc/wiki/Home and https://bitbucket.org/fispace/doc/wiki/spt

4.2.1.6 Software Development Toolkit (SDK)

The Software Development Toolkit (SDK) provides tool-support for the development of FIspace Apps. The SDK will ease the work of App developers during the implementation of the Apps, providing specific tools and hiding the complexity of the platform.

Particularly, the SDK will include:

Tooling (specifically an Integrated Development Environment, IDE), which is built on Eclipse. Eclipse is widely adopted by the development community and supported by the Eclipse foundation. The FIspace SDK will offer functionalities such as

• integration of Eclipse JDT (e.g., classpath containers) or Eclipse PDE;

• providing access to Javadoc for all referenced elements (FIspace modules) and auto-completion support;

• visual management of components and case modelling will be provided.

Libraries to link with the respective modules of the FIspace, such as security, privacy and trust, or the Cloud Service Bus (CSB).

Complementing the SDK, there will be a set of tools targeted to business architects for customizing and extending the FIspace to the individual needs of Users. This includes tools for authoring of Business Entities and Event Rules, as well as configuring mediators and connectors to backend systems.

Online documentation for SDK: http://dev.fispace.eu/doc/wiki/Home

4.2.1.7 Operating Environment

The Operating Environment ensures the technical interoperability and communication of (possibly distrib-uted) FIspace components and FIspace Apps and the consistent behaviour of the FIspace, including:

• A Cloud Service Bus (CSB) to support the interaction of FIspace components and Apps, which is based on peer-to-peer overlay technology, supporting (1) eventual consistency, (2) events bus, (3) management logic, (4) Pub/Sub abstraction for information dissemination, (5) a bulletin board abstraction for filtering and orchestration, (6) queues supporting various QoS for delivery and ex-ecution (e.g., once only or multiple readers);

• Replication and consistency service to ensure fault-tolerance and transaction support, which is partition tolerant and guarantees strong consistency (when needed);

• Facilitation of the management of the “composed service (application)” life-cycle, based on IaaS Cloud related OSS and BSS (planned to be provided by FIWARE);

• Operational registry for maintaining runtime attributes and supporting real-time operations;

• Multi-tenancy support, with the least effort from the developers (both FIspace developers and App developers);

• Monitoring of KPIs and health, automate the operation, enforce the SLA, facilitate the problem determination, continuous optimizing the runtime.

The Operating Environment provides automation supporting the application lifecycle and support a “scale out” design model that is decentralized with redundancy for failure tolerance and auto recovery. It sup-ports eventual consistency, as well as strong consistency asynchronous models.

Online documentation for Operating Environment: http://dev.fispace.eu/doc/wiki/Home

FInish 24.10.2014


4.2.2 FIspace demo and experimentation instance

An instance of the FIspace platform is available for demonstration and experimentation purposes. This instance can help manager, business architect, developers and end-users to use and understand what FIspace platform can offer at this moment.

For more information see the link below.

See: https://bitbucket.org/fispace/demostration-area/wiki/Home

4.3 FIspace initial APPs

The initial Apps can be found by End-Users in the App store. The FIspace App store is a tool-supported infrastructure for the provisioning, consumptions, purchase and re-use of IT-solutions for seamless busi-ness collaboration. Currently, there are different Apps developed and operational for the FIspace Plat-form.

Examples of some basic logistic Apps that are developed within FIspace are:

• Product Information App

• Logistics Planning App

• The Business Service Level Agreement Management App

4.3.1 Product Information App (PIA)

The main goal of the Product Information App (PIA) is to enable product information exchange between the stakeholders of a supply chain and towards the final consumer, based on the B2B collaborative and system integration capacities offered by the FIspace platform. The PIA enables the exchange of product related data (e.g. quality certificates, sensor data and data requests), and finally allow an access to infor-mation that flows via several nodes in complex supply networks. The PIA Initial App can provide this data in a raw way, or transform it into knowledge by means of rule-setting. The interaction with the FIspace platform will allow diffusing quality alerts related information to end consumers.

Main Features

• Easy and secure exchange of product related information between supply chain partners, both from a technical and business perspective, by avoiding centralised storage of information;

• Facilities for fine-grained access control over own product data by maintaining own data sources with adjusted access management;

• Provisioning of product information from trusted sources (certified by existing business relations from FIspace);

• Federation of decentralised product data sources to increase data availability.

• On-demand and real-time data access and update functionalities reducing duration and effort of data exchange;

• Allow the access to information that is generated/offered by the supplier(s) of the own supplier, enabling to access information spread in the supply network.

• Enabling bidirectional communication through the supply chain;

• By introducing attributes related rules, this App will provide relevant information for a stakeholder based on raw data. The aim is that data stored and gathered from different stakeholders is not di-rectly provided, but transformed by means of rules (an example of rules would be “if saturates are greater than 5,0 gr the level of saturates is high”).

The corresponding infrastructure will be provided by both local and FIspace based ICT resources. This Initial App will support diverse identification schemes and the easy and secure exchange of product relat-ed information between supply chain partners towards the consumer, both from a technical and business perspective, enabling bidirectional communication through the supply chain.

Therefore, the core objectives of the PIA Initial App are:

1. Provide to the single business actor (i.e. the person that interacts with the app)

o Capacity to add, modify, correct product information that shall be exchanged within the supply chain/network,

o Access product data that can be introduced by a stakeholder or generated by the PInfS

in raw data (data directly gathered from the stakeholders, i.e. data sets or key-value

pairs) or knowledge form (e.g. processed raw data by applying rules and patterns).

FInish 24.10.2014


2. Be compatible to diverse identification schemes,

3. Enable the decentralised storage of product related information.

More information about the PIA can be found in the FIspace Deliverable 400.6 http://www.fispace.eu/Documentations/Deliverables/FIspace-D400.6%20Functionalities%20of%20Baseline%20Applications.pdf

4.3.2 Logistics Planning App

The Logistics Planning App supports the generation and maintenance of transport chain plans by using the description of the demand, real time information of logistics services, real time contract information, execution statuses, and details of relevant events, as shown in Figure 6.

For the logistics service client (LSC), the baseline app supports the building of a transport chain plan based on the client's demand and online available services, using the latest available information for ser-vice descriptions.

For the logistics service provider (LSP), the baseline app enables the description of transport services that can be used by the LSCs, enables the use of marketplaces to find demands that match the provided services during planning time, as well as for planning the use of subcontractors.

For both clients and providers, the baseline app will have facilities for detailing out the execution plans and for negotiation and booking of the services. The app will also provide functionality for replanning, in case the execution of the original plans fails. In such case, user receives a notification indicating there is a problem. If needed; user can manually do the replanning by using LPA application.

Figure 6: Logistics Planning App Overview

More information about the Logistics Planning App can be found in the FIspace Deliverable 400.6 http://www.fispace.eu/Documentations/Deliverables/FIspace-D400.6%20Functionalities%20of%20Baseline%20Applications.pdf

4.3.3 The Business Service Level Agreement Management App

In this section we describe the Real-time Business SLA Management App (BizSLAM). The main purpose of this app is to bring into the operation of business activities the SLO (Service Level Objectives) estab-lished in the SLA (Service Level Agreement) between 2 partners. The difference of this SLA management solution for many others is the fact that services here are indeed real-life or cyber-physical services (e.g., transportation of goods by air carrier) and not computational services (e.g., buying a slice of storage from a cloud provider). Management of SLAs of cyber-physical services requires domain specific data models and different mechanisms to detect violations and to perform compliance check. Thus, this baseline app provide the solution for managing the information inside the SLAs of cyber-physical services (from now on called business services) and enabling notifications about events associated with the SLA information itself as well as violations on the SLOs established in this SLA.

The core capabilities of the Real-time Business SLA Management app are:

FInish 24.10.2014


Support for online representation of SLOs of business services.

Management of CRUD operations (Create, Read, Update, Delete) without compromising the pri-vacy and security of the stored SLAs.

Provide notifications about events and deadlines of each SLA a partner is part of.

Detection and signalling in real time of deviations on the SLOs of SLAs.

Notify partners about opportunities to establish SLAs.

More information about the Business Service Level Agreement Management App can be found in the FIspace Deliverable 400.6 http://www.fispace.eu/Documentations/Deliverables/FIspace-D400.6%20Functionalities%20of%20Baseline%20Applications.pdf

FInish 24.10.2014


5 Implementation Examples

Within the FIspace project several implementation examples (trials) are developed. The relevant exam-ples for the FInish project are the Fresh Fruit & Vegetables Quality Assurance Trial, Flowers and Plants Supply Chain Monitoring Trial, the Fish Distribution and (Re-) Planning Trial, the Meat Information Prove-nance Trial and the Import and Export of Consumer Goods trial.

The apps developed within these Trials can be reused and extended within the FInish Project.

For each trial we provided an introduction and a description of the trial specific apps that are currently in development.

5.1 Fresh Fruit & Vegetables Quality Assurance Trial

5.1.1 Introduction

The network of interconnected actors in the ‘Fresh Fruits and Vegetables Chain’ includes the following stages of the food chain (Figure 7):

Figure 7 : 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 centres that are responsible for sourcing, dis-tribution centres 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.

The FFV trial builds on 3 major Apps, the PIA (‘Product Information App’) which manages forward and backward information along the chain, BOXMAN (‘Inventory Management of RTI Packaging’) which man-ages the crates (boxes, containers, RTI) that carry the products from farms to retail, and RISKMAN that (in principle) quickly informs later stages of a chain if product deficiencies (quality, safety, residues, etc.) have been detected somewhere along the chain and, in turn, initiates appropriate action.

5.1.2 Trial Specific Apps

The trial Fresh Fruits and Vegetables build on 3 Apps. These 3 apps in themselves consist of a number of more limited ‘lower level’ Apps which are being connected via the FIspace platform. The Product Infor-mation App is being developed as an FIspace Initial App and adapted to specific needs of selected trial chains. This App is complemented by two domain specific Apps, the BOXMAN and RISKMAN App.

FInish 24.10.2014


5.2 Flowers and Plants Supply Chain Monitoring Trial

5.2.1 Introduction

The management of product quality is of vital importance in supply chains of fresh produce such as flow-ers and plants. The floricultural industry currently uses data loggers that record sensor data of quality conditions such as temperature and humidity. However, these data are only tracked afterwards and not in real time. The combination of new technologies for tracking and tracing (e.g. RFID), quality monitoring (e.g. wireless sensor networks) and internet connectivity (e.g. cloud computing and web services) ena-bles real-time management of product quality in a supply chain context.

This pilot demonstrates the possibilities of Future Internet technologies for dynamic Quality Controlled Logistics in floricultural supply chains. In this approach, logistic processes throughout the supply chain are continuously monitored, planned and optimised based on real-time information of the relevant quality parameters (such as temperature and humidity).

This trial concerns 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. 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 re-maining shelve life. Implementation of these functionalities is expected to result in:

significant reduction of product waste throughout the supply chain;

shorter lead times;

better capacity utilization;

improvements in product quality for end-consumers.


In the Flower and Plant Supply Chain Monitoring Trial different Apps will be developed. In the Figure be-low an overview of these Apps is provided.

Figure 8: Relations between the Apps in the Flowers and Plants Trial

5.2.2.1 App 1. Item Tracking and Tracing (ITT App)

An App for Item Tracking and Tracing of cut flowers and pot plants. With this App participants in the plant and flower supply chain are able to determine the location of products or lots real-time

In Figure 9 (Inbound) and Figure 10 (outbound) an overview is given of the logistic processes incorpo-rated in the App. Modelling these processes enables each trade partner to know real-time at which loca-tion a product is.

FInish 24.10.2014


Figure 9: Experiment 1A. Overview of business 2 business logistic inbound interactions

Figure 10: Experiment 1B. Overview of business 2 business logistics outbound interactions

FInish 24.10.2014


5.2.2.2 App 2. Conditions Monitoring (CM App)

An App to monitor environmental conditions: temperature, humidity etc. This App enables product owners to monitor relevant conditions influencing product quality real time. By comparing current values of condi-tions such as temperature, air humidity and luminance with boundary values suitable for the product at that specific location, alarm signals can be generated if boundary values are exceeded

Figure 11: Overview of the Condition Monitoring App

In Figure 11 an overview has been given of the processes modelled in the Conditions Monitoring App. The main environmental conditions affecting product quality are temperature, relative humidity and light intensity. Conditions will be monitored at fixed locations such as cold stores and moving locations such as trucks.

5.2.2.3 App 3. Expert Quality Assessment (EQA App)

An App to Assess Quality of the products by Experts. Experts can assess the quality of the product at any time throughout the supply chain and store the data by using the App. In this way it enables product own-ers to follow the quality decay throughout the whole trade chain.

Figure 12: Overview of the processes modelled in the Expert Quality Assessment App

FInish 24.10.2014


5.2.2.4 App 4. Product Quality Alerts (PQA App)

An App generating Quality Alerts based on Product location, conditions on location and quality assess-ment. If quality boundary values are exceeded during transport and storage, quality alerts are generated triggering supply chain managers to intervene in order to safeguard product quality.

In Figure 13 an overview of processes modelled in the PQA App is given. This figures explains how data generated by the ITT App, the CM App and the EQA App are combined with product norms in order to assess whether norm values are exceeded, thus generating an alert.

Figure 13: Overview of processes modelled in the Product Quality Alerts App

5.2.2.5 App 5. Quality Decay Prediction (QDP App)

QDP is an App to Predict the Quality Decay given the current quality and conditions of the product and expected quality development based on the initial product quality. This App supports the supply chain manager to predict the quality of the product throughout the supply chain given the conditions the product has been subject to in the previous stages of the supply chain. This enables the supply chain manager to assess whether the product still meets the required quality standards at subsequent stages of the supply chain, and especially when it arrives at the consumer, and if interventions are necessary.

In Figure 14 the relations between the Quality Decay Prediction App and the Product Quality Alerts are explained. Product quality assessment data and alerts can be combined with cultivar specific decay algo-rithms known from literature to predict the quality decay. This information can be used in the Quality con-trolled Planning App to adjust the destination if the quality decay is unacceptable for the current destina-tion. The time series data generated by the ITT, the CM and the EQA App can also be used to sharpen norm values by application of self-learning models.

FInish 24.10.2014


Figure 14: Overview of headlines of processes to be modelled in the Quality Decay Prediction App

5.2.2.6 App 6. Botanic Information (BOTAPP)

The BOTAPP application enables product owners to register flowers and plants in a sector-specific prod-uct information database and any other users including consumers to get access to certain specific prod-uct information like botanic information of the cultivar, including taxonomic numbers, product numbers, trade names, botanical characteristics and standardized product picture), treatment instructions, repre-sentative pictures of the cultivar or even lot-specific photographs of the product.

5.3 Fish Distribution and (Re-) Planning Trial

5.3.1 Introduction

The fish trial is concerned with the planning of logistics and transport activity in the fish industry, a crucial process for ensuring performance across the whole supply chain. The main challenges addressed are low predictability of transport demand and late shipment booking cancellations, mostly due to lack of col-laboration or access to information, affecting directly the resource and asset utilization of service suppli-ers (carrier, terminal). Furthermore, data quality at the planning phase is essential for enabling effective monitoring of transport execution.

The trial is built on a case of export of fish from Norway: Fish exporters produce fish products (dry and frozen) continuously, 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 declara-tions, follow up, and tracking and tracing of cargo. The carriers are responsible for shipping the fish cargo from Ålesund to continental Europe, then overseas. Carriers receive bookings continuously as well as cancellations, which they need to handle in the best possible way in order to maintain an acceptable level of capacity utilization. Trial "Fish distribution (re)planning" focuses on the feedering part of the transport chain, i.e. shipping from Norway to continental Europe.

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

FInish 24.10.2014


• 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 (e.g. lack of import license from country of destination).

• Transport demand (re)planning: for the carrier, this includes demand planning/forecast, re-source management and (re)planning of transport operations in case of deviations.

• Tracing of cargo: tracing of cargo for detecting deviations at the planning phase (e.g. delayed cargo before reaching the port terminal).

The trial will strive for improvement of the following aspects, with focus on the carrier role:

• Improved Booking Reliability: improved upstream planning so that the carrier gets more visibil-ity, more reliable booking, and early notification of changes. The trial will demonstrate how a bet-ter integration of the supply chain, in terms of information distribution and accessibility, can con-tribute 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 poli-cies that encourage early booking and dissuade dummy booking and late cancellations, this solu-tion is believed to have a strong positive impact on capacity utilization as well as cost efficiency, especially for the short sea shipping spot market.


In the Fish Distribution and (re-) Planning CargoSwApp will develop an application for matching the transport demand of a shipper with the transport service offered by a logistics service provider or a carri-er, such as a shipping company, in an ad-hoc manner. This means that the feature to be highlighted is the immediate search-and-find option of both parties for realizing the transport process. CargoSwApp is a central part of the Fish Distribution (Re-) Planning Trial. It uses functionalities from the “Marketplace Op-erations Service” and input from the backend booking systems. The App is used both for late cancella-tions in order to try to fulfil a promised service level agreement and improvement of vessel utilizations. It will assist carriers in dealing with late cancellations and finding new business partners with their load in the very short run.

5.3.2.1 CargoSwapApp

Figure 15 shows te interaction for the CargoSwApp at the process level, The CargoSwApp will have in-teraction with the MOA for doing match-making of transport demands and transport offers, for the LPA for fetching transport demands, and cancellations, and with Softship, the booking system of the carrier to fetch voyage data and available vessel capacity data.

FInish 24.10.2014


Figure 15: CargoSwApp Process

5.4 Meat Information Provenance Trial

5.4.1 Introduction

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 FIWARE 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-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.

FInish 24.10.2014


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.


5.4.2.1 Farm Capture App

This App will be developed to collect and capture EPCIS events at the farm (i.e. breeder and fattener) that do not have an ERP system to provide events such as birth, transfer of animals to other farms and slaughterhouse. This App will be designed and implemented as a simple web form. The basic capturing functionality of the meat transparency system will translate the information into standard EPCIS events and store these in an EPCIS repository.

5.4.2.2 Query EPCIS Repositories App

This App shall support standard EPCIS query operations (i.e. queries for specific business locations, pro-cesses, products, time intervals, etc.). For instance, by entering or scanning the product and batch/serial number of an end or intermediate product, the App will provide all information related to that product (e.g. “Where does it come from?” “When did it arrive?” “What raw material was used to produce it?”). Author-ized parties such as business partners, authorities or regulators will be enabled to trace where a specific product is – for instance, in case of product recall.

5.4.2.3 Discover EPCIS Repositories App

This App covers the functionality to discover which business party has information about a specific object (for instance, a product identified via Global Trade Item Number (GTIN) + lot or serial number or a ship-ment identified via a Serial Shipping Container Code (SSCC)) in order to (re)construct the entire chain of custody of a given end or intermediate product. As such information is of competitive nature, only parties which are both authenticated and authorized shall be allowed to execute such an operation. In this con-text, an administration Application has to be developed in order to allow specifying which companies/ authorities (and under which conditions) shall have access to traceability information

5.4.2.4 Aggregating Traceability Information App

This App covers the automated collection and aggregation of traceability information about a given end or intermediate product and their presentation in a web-based graphical user interface in a user-friendly manner. At least the following information shall be displayed as soon as an authorized requester enters the id of an event that implies a food alert. An example of such an event might be a measured salmonella contagion that exceeds a certain norm. It might involve all products that were at a specific location within a specific time window. In that case the App should receive that event as input and produce all tracking and tracing data that have this event in their "event chain”.

1. place/ date of birth, date/ location of slaughtering of the processed animals; 2. list of all parties who had custody of a product; 3. list of distribution centres/ retail stores a product of concern has been shipped to.

Consumer App

This App is a “consumer” variant of the Aggregating Traceability Information App. Its functionality shall provide an agreed subset of traceability data to consumers. Thereby, the App consolidates not only dy-namic data (date of slaughtering, place of birth, etc.), but also static data on a product (e.g. weight, ingre-dients) and partly master data (e.g. location of the slaughterhouse) as well as marketing information (pic-tures, certificates, videos, etc.) about a given product. It doesn’t however allow tracking of products, as the Aggregating Traceability Information App does.

FInish 24.10.2014


5.5 Import and Export of Consumer Goods

1.1.1 Introduction

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 16: 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:

1. 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 management of the transport service, i.e. transport order & booking and organizing the exe-

FInish 24.10.2014


cution of an inbound process for Arcelik. The story is built planning of the transport of materi-als 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 poten-tial partners for collaborating without heavy manual intervention. Potentially it is expected to increase the visibility of SMEs in global business collaboration. Increased visibility of the pro-cesses and automated notifications for deviations can lead to a more intelligent supply plan-ning which lead to more effective supply chains.

2. 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 optimisation with effective and proactive deviation man-agement 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 in-volved parties.


In this trial three Apps are in development: The Transport Demand App, The Shipment Status App and the Manual Event & Deviation Reporting App.

The Transport Demand App will be used to create an initial demand description (freight unit) and make it available to other users and FIspace Apps.

The Shipment Status App will improve the information exchange between shippers and consigners in the Shipment process status, allowing the users to identify the transport of interest, to consult the transport plans either by shipment view (i.e. showing all shipments of interest in a compact view) or by product view (i.e. the entire transport plan for a given item).

The Manual Event & Deviation Reporting App will allow the handling of the actual execution of shipments by the user responsible (i.e. logistics responsible, warehouse responsible, carriers) and the reporting of the:

Deviation from the plan: they will be able to associate a new deliver time/date to a given check-point, and add comments or justifications.

Events, which do not imply a delay, but that may be relevant for other users

5.6 Wrap-up

In sum, within the FIspace project several applications are being developed that will be included in the FIspace App store. These Apps could be very valuable for FInish Apps. Developers could learn from its design and reuse functionalities provided by these Apps (in mash ups) in order to prevent re-inventing the wheel. An overview of the Apps is presented in Table 1.

Table 1: Overview of Apps being developed within the FIspace project (see: www.fispace.eu)

Trial App Description

Initial Apps Product Information App This app is designed to facilitate the exchange of quality-related product information that flows between steps in complex (food) supply networks. Its purpose is to enable stakeholders in a food supply chain to exchange quality-related product information across corporate boundaries, including hori-zontal collaboration with service pro-viders, laboratories, etc

Initial Apps Logistics Planning App The main functionality of this app is to provide the support for automated planning of logistics services.

FInish 24.10.2014


Initial Apps The Business Service Level Agreement Management App

This app will help to create, manage and store your business agreements in real time, it supports basic create, update and delete operations with involvement and acceptance from your partner. It also updates you on SLO violations, flag expiry events and noti-fication from partners to delete or make any changes to agreed SLOs.

Fresh Fruit & Vegetables Quality Assurance Trial

BOXMAN This app targets to simplify the man-agement of different utilized RTIs by various Pool Management Organiza-tions used within the supply chain.

Fresh Fruit & Vegetables Quality Assurance Trial

RISKMAN RISKMAN provides risk information (laboratory analysis, callbacks of products, press reports, etc.) along the supply chain and reports it to the us-ers. RISKMAN is an early warning system, which provides all players of the supply chain with information on critical issues (i.e. food safety).

Flower and Plants Supply Chain Monitoring

Item Tracking & Tracing Application for Item Tracking and Tracing


Conditions Monitoring App to monitor environmental condi-tions.


Expert Quality Assessment The EQA is an app for registering quality assessments of floricultural products made by quality experts and inspectors.


Product Quality Alerts This app will allow generating Quality Alerts.


Quality Decay Prediction This app to Predict the Quality Decay given the current quality and condi-tions of the product and expected quality development based on the initial product quality.


Botanic Information This app acts as a botanic product information broker. The several parties in the supply chain will be able to gain relevant information on products of flowers and plants. Also feedback can be given to the product owners of these products.

Fish Distribution and (Re-) Planning Trial

CargoSwappApp This app is used by a Logistics Ser-vice Provider (e.g. a carrier, a contain-er line operator) for finding replace-ments for cancelled orders and filling empty cargo space on the vessel on relatively short notice.

Meat Information Provenance Trial

Farm Capture App This app enables farmers to copy animal passport data (and more) as EPCIS events and master data on

FInish 24.10.2014


other aspects to an EPCIS repository.


Query EPCIS Repository App

This app shall support standard EP-CIS query operations (i.e. queries for specific business locations, processes, products, time intervals, etc.).


Discover EPCIS Repository App

This app covers the functionality to discover which business party has information about a specific object (for instance, a product identified via Global Trade Item Number (GTIN) + lot or serial number or a shipment identified via a Serial Shipping Con-tainer Code (SSCC)) in order to (re)construct the entire chain of custo-dy of a given end or intermediate product.


Aggregating Traceability Information App

This app covers the automated collec-tion and aggregation of traceability information about a given end or in-termediate product and their presenta-tion in a web-based graphical user interface in a user-friendly manner.

Import and Export of Con-sumer Goods

Transport Demand App This app will be used to create an initial demand description (freight unit) and make it available to other users and FIspace Apps.


Shipment Status App This app will improve the information exchange between shippers and con-signers in the Shipment process sta-tus, allowing the users to identify the transport of interest, to consult the transport plans either by shipment view (i.e. showing all shipments of interest in a compact view) or by prod-uct view (i.e. the entire transport plan for a given item).


Manual Event & Deviation App

This app will allow the handling of the actual execution of shipments by the user responsible (i.e. logistics respon-sible, warehouse responsible, carriers) and the reporting of the:

Deviation from the plan: they will be able to associate a new deliver time/date to a given check-point, and add com-ments or justifications.

Events, which do not imply a delay, but that may be rele-vant for other users

FInish 24.10.2014


6 Building Future Internet Apps in FInish

6.1 Customized User Systems

The aim of the FI Apps developed within the FInish project is to realize components that use FIWARE and FIspace software and that can enable a customized user system for actors of perishable supply chains.

The realization of customized user systems is achieved by means of two key mechanisms

• Addition of functionality through Apps: Apps will provide value added services and wrapped software capabilities; Apps thus aggregate capabilities in a reusable fashion such as to become attractive for many users.

• Configuration through collaborative workflows: Allowing Apps to be composed along collabo-rative workflows and mashed-up into personalized dashboards for users. In addition, FIspace can be configured to allow flexible integration of data sources of users and linking those data sources to Apps along collaborative work-flows.

As a consequence, the FIspace architecture identifies three major types of stakeholders:

• App Developers: the software and system providers who offer ‘packaged’, componentized solu-tions and applications in form of Apps;

• Business Architects: the experts (internal or external to the user organization) that are in charge of pre-configuring FIspace for their individual business needs; particularly they will design and de-fine customized collaborative workflows and connect those workflows with FIspace Apps and backend systems;

• End Users: the actual (industry) users of the collaboration services and Apps provided by FIspace; those will be supported in their daily business activities, with special focus on their inter-action and collaboration with business partners; examples of those users include farmers, ship-pers, freight forwarders, cargo carrying airlines, and regulatory agencies;

6.2 Guideline for the development of Apps within the FInish project

1) Find existing Apps to build upon

Relevant Apps to build upon can be found in the FIspace App Store. The suitability and re-usability of these Apps (features, functionality, technical details, pricing models, terms & condition for re-use) should be investigated. The App Store module supports this activity by providing App search and discovery facili-ties, support for detailed investigation, App purchase support for re-use and ratings of Apps by FIspace community. (For links to related documentation see Table 2)

2) Find existing standards to build upon

Existing standards should be used to develop FInish Apps. Links to documentation about available standards for Apps in the Food and Flower domain can be found in Table 2

3) Develop App

The App development can be supported using the FIspace Software Development Toolkit. The FIspace Software Development Toolkit supports to develop an App that complies with the FIspace operational model and to define the provided interface (including functions that can be called and data/events re-quired by App). The Software Development Toolkit of FIspace provides tools to support App develop-ment, to ensure the compliance with FIspace operational model and frameworks (UI technology, technical interfaces & interaction protocols, security techniques) and to link with libraries required to connect to FIspace Cloud Service Bus (Operating Environment) and Security Privacy and Trust mechanisms. The FIspace platform uses FIWARE technology enablers to realize its functionality. On top of FIspace, app developers can also make directly use of the FIWARE enablers for implementing specific features. These enablers are available via the FIWARE software catalogue (For links to related documentation see Table 2)

FInish 24.10.2014


4) Publish new App in App Store The Apps developed within FInish need to be published in the FIspace App store by creating an App de-scription (including required / provided interfaces, definition of pricing models, usage terms & conditions) and conducting the FIspace App publication process in the App Store module. (For links to related docu-mentation see Table 2)

5) Create customized solution

This activity comprises three specific tasks. First, the B2B Core module is used to design a desired work-flow for users, which includes a specification of the sequence of Apps, data models and relevant systems and the interaction and collaboration with business partners. The platform applies the guard-stage-milestone approach for specifying business entity lifecycles in order to support the dynamic workflows and diverse interactions as Apparent in collaborative business networks [9]. Second, the designed work-flow is used to integrate the selected Apps, which includes the detailed configuration of Collaboration Artifacts and Event Rules, the customization of the selected Apps (hide or rename data fields, or add additional functionality) and finally the detailed specification of the ‘mash-up’ execution sequence and technical interaction models. Third, the System and Data Integration facilities (including application con-nectors and data mediators) are used to map and connect relevant systems (‘legacy’ systems and exter-nal systems & services) and integrate them into the customized workflow. (For links to related documen-tation see Table 2)

6) Provide customized solution to users

The customized solution needs to be made accessible in the personal User Front-End for relevant users, including pre-configuration of access rights and personalization of user-specific notifications and commu-nication facilities by using the Security, Privacy and Trust module. This activity also includes the configu-ration of specific pricing and payment options with the support of the App Store’s revenue sharing facili-ties. (For links to related documentation see Table 2)

7) Use Apps and the FIspace platform features for conducting daily business

The FInish Apps should be used for conducting daily business including definition of specific notification and communication settings for business activities, usage of collaboration features for specific business activities and transactions.

8) Provide App Documentation to FInish FInish requires App documentation including a description of the capabilities and adopted standards.

Table 2: Steps to develop FInish Apps and the related documentation

Step # Step name Related documentation

1) Find existing Apps to build upon

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

2) Find existing standards to build upon

SmartAgriFood Deliverable D300.4 (www.smartagrifood.eu)

FIspace Deliverable 500.4.1 (www.fispace.eu)

3) Develop App http://dev.fispace.eu/doc/wiki/Home

http://www.fispace.eu/

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

4) Publish new App in App Store


5) Create customized solu-tion


6) Provide customized http://dev.fispace.eu/doc/wiki/Home

FInish 24.10.2014


solution to users

7) Use Apps and the FIspace platform fea-tures for conducting daily business

8) Provide App Documen-tation to FInish

FInish 24.10.2014


7 References

1. Vorst, J.G.A.J.v.d., Effective food supply chains: generating, modelling and evaluating supply chain scenarios2000: Wageningen Universiteit.

2. Christopher, M., Logistics and supply chain management: creating value-adding networks2005: Pearson education.

3. FoodDrinkEurope, Data & Trends of the European Food and Drink Industry 2013-2014, 2014, pp. 25

4. Verdouw, C., et al., Smart agri-food logistics: requirements for the future internet, in Dynamics in Logistics2013, Springer. p. 247-257.

5. Verdouw, C.N., et al., Future Internet as a Driver for Virtualization, Connectivity and Intelligence of Agri‐Food Supply Chain Networks. International Journal on Food System Dynamics, 2014. 4(4): p. 261-272.

6. Verdouw, C., A. Beulens, and J. Van Der Vorst, Virtualisation of floricultural supply chains: A review from

an Internet of Things perspective. Computers and Electronics in Agriculture, 2013. 99: p. 160-175.

7. Metzger, A., et al., FIspace Technical Architecture and Specification, 2013, FIspace.

8. Di Nitto, E., et al., A journey to highly dynamic, self-adaptive service-based applications. Automated Software Engineering 2008. 15(3-4): p. 313-341.

9. Richard Hull, et al., Introducing the guard-stage-milestone approach for specifying business entity

lifecycles, in Web Services and Formal Methods 2011. p. pp 1-24

consolidate trials and identify business demands for ... · consolidate trials and identify...

Documents