Section 1 - Use Case Descriptions

The use cases for the TagItSmart project were created by combining expertise of consortium partners. Total five use cases will be implemented during the project. Table 1 summarises the use cases.

Table 1. Summary of use cases to be implemented in TagItSmart! Project together with consortium partners.

Use case Owner Partners

Digital product UpCode FLE, UNIS, VTT, EVT, UNIPD, UPC, SIE, DUR

Lifecycle management DONDE DNET, FLE, EVT, UNIPD, UPC, SIE, TF, UNILEVER, DONDE, DUR, UNIS

Brand protection DURST DNET, VTT, EVT, UNIPD, UPC, SIE, TF, DURST, UNIS

Condition dependent pricing Univerexport DNET, FLE, UNIS, VTT, EVT, UNIPD, UPC, TF, UNIEX, DUR, UNIS

Home services PICOM DNET, UNIS, EVT, UNIPD, UPC, PICOM, DONDE, DUR

The digital product use case is a kind of umbrella use case including the whole value chain from manufacturer to transport, retail, consumer and recycling, see Figure 1. The other use cases concentrate more in detailed to one or two stages of the lifecycle of the product.

Figure 1. The TagItSmart! use cases under the Digital product umbrella.

Page 1/13

1.1 Digital product

This use case is based on fast-moving consumer goods (FMCG) that want to become “smart” via SmartTAG and TagItSmart. In this use case the manufacturers are able to control products that leave their factories throughout their lifecycle, e.g. where and how the products are transported and in which conditions, when they have been delivered to the retail stores and when sold to the consumers. This use case also creates a new channel for manufacturers to communicate with the consumer, so that they can enable easy access to related information on product and item-level which is not only static but depend on lifecycle and historical data of the item.

Figure below describes high-level features that Digital Products implements, these features act as guidelines when requirements for Digital Product are developed.

Figure 1.- Digital Products use case featuresDuring Digital Products lifecycle following events happen, each of these events gives information to requirements development, as shown in Figure 2.

Page 2/13

Figure 2.- Digital Products use case conceptual flow

1.2 Lifecycle Management/Recycling

The lifecycle management/recycling use case is built around the concept of consumers buying products in the supermarket and engaging with them in different ways, focusing on the recyclability of the product, creating an ecosystem where consumers are provided with information about how to recycle a product based on contextual information (location, local regulations) and product recyclability (materials); information that is linked to the SmartTags on the products.

SmartTags in this use case enable the creation of consumer oriented services that are based on information that has been generated at different stages of the lifecycle of a product, involving different stakeholders, from the brands, to the retailers as well as the ultimate focus, the consumers and the authorities that regulate the recycling policies.

Page 3/13

Figure 3.- Lifecycle Management/Recycling use case conceptual flow

1.3 Brand Protection

The brand protection use case aims at providing brands and consumers with a mechanism to test authenticity of their products and reduce counterfeiting. SmartTags and their capabilities to change based on environmental conditions (such as light, temperature) are used to first identify uniquely the item at hand and second to provide means to avoid fake or misplaced products, by enabling contextual scanning.

How do we know thisparfume originates from

WellOdor Corp.?

??

?

Lets check the Smart Tag at the backside of

the bottle!!

!! By reading the QR-code on the label once

it guides me to the„Proof me if you can“

service fromTagItSmart!

Proof meif you can!

This is the TagItSmart! „Proof me if you can“ service for originality

proof.

Please read the codeagain by swithing on the

flashlight of yourhandheld device or

download the proper reader here.

Yes, I am“Parfum”

by

WellOdor Corp.

Proof meif you can!

After the 2nd read the„Proof me if you can“

service approvesoriginality of „Parfume“

by WellOdor Corp.

Figure 5.- Brand protection use case conceptual flow

1.4 Dynamic Pricing

Manufacturing first provide general information about the products (ingredients, recycling information, best before, consumable before, etc.) as well as reference thresholds for the

Page 4/13

type of the product. Then the SmartTag (ID) is encoded and SmartTag is printed and attached to the product package. As a part of internal process control, the manufacturer scans SmartTag while the product is still in the factory (meat processing plant). Then the product is ready for transport to the retailer. Afterwards, the transport provider scans SmartTag as a part of the process control. In retail, retailer provides additional information about the products to support consumers (recipes, how to use etc.). Availability of information defined: general or when scanned at selected locations only (in their shops). Then the retailer scans SmartTag as a part of “supply chain control process “. Scanning results (pack ID and result) are forwarded to platform and dynamic price calculation process is invoked. Consumer scans SmartTags using a smartphone application and obtains information about the product (best before, price, recycling, recipes and other info approved by retailers). The retrieved information depends on the location and time of scanning.

Figure 6 Dynamic pricing use case conceptual flow

1.5 Home Services The Home Services use case has the following general scenarios and flows:

1) Purchase a. A Smart Tag needs to be installed by manufacturer and/or printed by retailer for

the customer to starts the warranty information.b. Retailer can gather information about purchaser.c. Manufacturer gets notification about purchase for statistics (price sold).d. Logistics gets notification about replenishment/relocation stocks.

2) Installationa. A technician scan tag and retrieves installation manuals.b. The user confirms authenticity/warranty via scan.c. The customer gets a user guide/application on his personal device via scan.

Page 5/13

3) Correct Operation:a. Energy tips are given at scanning.b. Context information is gathered combining context readings and energy

consumption measures.4) Maintenance Operations:

a. Scans notify the time available to next maintenance action.b. Service Providers provide quotes/meeting dates.c. After maintenance, the tags are reset, or re-printed.

5) Water Qualitya. Read SmartTag about water quality/high temperature exposure and if contains

tartar/limestone.b. Order Tartar Limestone Inhibitorc. Reset the Tag after replacement.

6) Malfunctioning Alert:a. High temperature is recognized via scan and confirms whether warranty is in

place or not.b. Prove correct operations via scan tagc. Order repair service

7) Air Safety:a. Environmental Sensors provide information about gas leakages.b. Alert when reading Tag, Recommendation to open windows (trigger smart

actuator).c. Notification when air is safe.d. Replace Tag or reversible ink.

8) End of Life:a. Scan notifies that the end of life has been reached.b. Recycling services are informed and provide info for recycling point.

Page 6/13

Figure 4.- Home Services Use Case conceptual flow

Section 2 - Functional Components and Services

Page 7/13

Based on the use cases, we defined which platform components could fulfil the requirements for the different use cases. Based on the different aspects, we can group the different components in the following groups:

Service Management: defines components needed to access, discover and execute services in the platform.

Virtual Entities: defines components to work with virtual representations of the different objects defined in the use cases, from a CPG product to a sensor in a boiler.

SmartTags: defines the components to manage the creation, scanning and management of SmartTags.

Security: defines the components that will implement the authentication, authorisation, and any other security related aspects of the platform.

Domain Management: defines components that are specific to a use case domain.

Utility Services: defines utility components with services shared across use cases.

Application Development Tools: defines the SDKs and tools needed to implement applications on top of the platform.

Each group defines components to cover the different functional areas. Each component can be classified as one of the following types:

Service: software component with internal logic and providing an API. Data Store: any form of persistent storage technology. Semantic Model: semantic description of the related entity. Tools/Library: software component intended to be used in the development of

applications using TagItSmart technology. UI: visual component that serves as the interface for users of different roles to interact

with the rest of the components.

Section 3 - Architecture

The TagItSmart! platform from the functional point of view is composed from User/Developer level that provides front end for the different components, Service level for provisioning of the services and related functionalities and Virtual Entity level which is actual representations of the objects and provides access to the data and defined actions based on the semantic models.

From the current reference Architecture model defined, the SmartTag (blue box), the Data Access (orange box) and the User/Developer environment (green box) are planned to be released as separate open source modules. In this manner, anyone should be able to use its own platform and or/modules and plug on top of it components developed by TagItSmart!.

Page 8/13

The components defined in are the set of components needed to fulfil the requirements extracted from the different use cases, while enabling the creation and lifecycle management of the SmartTags.

Based on the chosen integration strategy the mapping of some of the components to real implementations and deployments in a specific IoT platform will be different. However, TagItSmart components will define a common API to guarantee interoperability and seamless integration, as well as enabling the creation of third party applications on top of its components.

We propose the definition of the functionality needs in a simple HTTP REST based API for the main components that will govern the composition of services and the management of the SmartTags. Once the models developed in WP2, 3 and 4 are consolidated, the payloads and additional resources will be formalised. Additionally, the API can be mapped to other transport protocols, like MQTT, which will give support for push messaging to the different components.

Table 2.- Preliminary API Design Component HTTP

methodResource Purpose Input

PayloadOutput Payload

Service Access

Interface

GET /services List all available services

N.A. Array of available service descriptions

Page 9/13

Component HTTP method

Resource Purpose Input Payload

Output Payload

POST /services Create a new service description and make it available in the platform

Service Description

Service Identifier

GET

PUT

DELETE

/services/{id} Retrieve

Update

and Delete

a service description in the platform

N.A.

Service Description updates

N.A.

Status

GET /templates List all available templates in the platform

N.A. Array of available templates

POST /templates Create a new template and make it available in the platform

Template description

Template Identifier

GET

PUT

DELETE

/templates/{id} Retrieve

Update

and Delete

a template description in the platform

N.A.

Service Description updates

N.A.

Status

Service Manager

POST /services/query Create a semantic query for services or templates

Query Description Inputs and Outputs needed

Array of Services matching the query

POST /templates/query Create a query to resolve correspondent services needed for the execution will be selected.

Query description type of template needed.

Returns the correspondent workflow to execute.

Workflow Manager

POST /workflows/{id}/action/execute

Executes a workflow as defined by the Service Manager

Workflow template filled with all the needed information for the execution

Workflow Identifier

GET /workflows/{id} Gets the information of a workflow and its state

N.A. Workflow description and status

Virtual Entity Access

Interface

GET /virtualentities List all available entities N.A. Array of Virtual Entities matching the query

GET

PUT

DELETE

/virtualentitites/{id}

Retrieve

Update

and Delete

a virtual entity in the platform

N.A.

VE Description updates

N.A.

Status

POST /virtualentities/query

Create a semantic query for virtual entities

Query Description

Array of virtual entities matching

Page 10/13

Component HTTP method

Resource Purpose Input Payload

Output Payload

the query

Identity Management

POST /virtualentities Create a new entity assigning a unique identity

Virtual Entity Description

Web Identifier

SmartTag Creation

POST /virtualentities/{id}/smarttags

Creates a new SmartTag and assigns it to the correspondent Virtual Entity

SmartTag Description

Identifier

GET

PUT

DELETE

/virtualentities/{id}/smartags/{id}

Retrieve

Update

and Delete

a SmartTag in the platform

N.A.

VE Description updates

N.A.

Status

SmartTag Printing

GET /virtualentities /printers

List all available printers N.A. Array of printers available

POST /virtualentities/preprint

Registers a printer description

Printer Description

Identifier

POST /virtualentities/printers/query

Create a semantic query for printers

Query Description

Array of printers’ entities matching the query

POST /virtualentities/printers/{id}/action/print

Sends a print action and returns the corresponding printing results

Print action description

Status and identifier

GET /virtualentities /printers/{id}/action/print/{id}

Gets the status of a printing action

N.A. Status of the printing process

1 TagItSmart components available for the Open CallComponent DescriptionSmartTag Encoding, Creation and FC-Scanner (Javascript Web based SKD) for EVRYTHNG platform.

Web based components that enables the development of web applications that use SmartTags (functional inks and NFC) (Javascript SDK).

Virtual Entity Access Interface API endpoints to create Virtual Entities that have SmartTags associated. EVRYTHNG will provide backend support with free access to their IoT Smart Products Platform. Documentation can be found here: https://developers.evrythng.com/docs/

Stream Processing Ability to process the SmartTags information in real time and send events. EVRYTHNG will provide backend support with free access to their IoT Smart Products Platform. Documentation can be found here: https://developers.evrythng.com/docs/

Page 11/13

Identity Management Ability to create unique Web Identities of Virtual Entities to be used with the SmartTags. EVRYTHNG will provide backend support with free access to their IoT Smart Products Platform. Documentation can be found here: https://developers.evrythng.com/docs/

User Management/Authentication/Access Control

Ability to capture interactions from the applications and the SmartTags and define custom analytics that can be used in applications. EVRYTHNG will provide backend support with free access to their IoT Smart Products Platform. Documentation can be found here: https://developers.evrythng.com/docs/

Data Analytics Ability to capture interactions from the applications and the SmartTags and define custom analytics that can be used in applications. EVRYTHNG will provide backend support with free access to their IoT Smart Products Platform. Documentation can be found here: https://developers.evrythng.com/docs/

SmartTag Encoding, Creation and FC-Scanner (Xamarin Mobile based SKD and ASP.NET MVC Web based SDK).

QR code SmartTag Scanner SDK is component that takes QR code as an input and gives alphanumeric string as an output. SmartTag QR code building SDK is component that supports generation of the QR code by enabling its customized creation based on input alphanumeric (SmartTag value) string and number of sensors. As an output SDK will generate QR code with embedded alphanumeric value and sensor positioned in defined space.Web Provisioning tool is a SDK developed as a web application with following functionalities:

access control and user management (CRUD - username, pass, phone, email, gender, age);

product creation (with QR code building module: number of sensors (printed ink parts), product specification, price, "how to use manual", description, etc);

retail accounts management, product management, etc.

create batch QR codes for selected product

Fujitsu’s Coelition Date Engine A secure, cloud based, Coelition standards compliant repository for storing information about human behaviour. In the context of TagItSmart, the Data Engine can be used to store the results of a tag scan, but more importantly it can store the context information (time, location, social context, etc.) of the scan event. This can include GDPR-Ready consent and related functionality (e.g. the right to be erased). The Coelition Data Engine is also available for commercial use following a successful trial. For more information about Coelition, see www.coelition.org.

Workflow Enforcer and SmartTag Scanning Module

Open Call participants can choose to build their application on Fujitsu RunMyProcess business

Page 12/13

process integration platform. Integrating 1000s of existing business components into a single deployable application. The mobile app includes a built in smart tag reader to capture the contents of TagItSmart smart tags. For details see: www.runmyprocess.com

Smart Tag Design service The design of a QR code that can be read by standard QR code readers in two different ways (before and after exposure to an environmental influence) requires a complicated technical process. Based on a root URL (e.g. www.example.com/product002/) we will generate on request two URLs and corresponding QR codes. We will provide example codes for both the before and after states and the mask that would need to be printed in reactive ink. For example:

SmartTag module (creation, scanning, decoding)

Code creation (VE’s). Scanning FC (DM) codes in mobile

Android based user authentication An authentication method which uses the user location and location history to authenticate a user.

Semantic parser A biometric technique to authenticate users on mobile devices by using their typing behaviour.

NFC opensense, SpeedTap, Temperature labelsPrinting of inks and information about the availability

Analog printing (flexography) of thermochromic and photochromic inks. Partners also free to print at other places. Recommendations on where to find suitable commercial inks.

Inkjet printing of tags (1) CMYK inkjet printing of tags with standard ink set using Durst "Roh" printer series (Lienz) on customer substrates; if customer substrates are not available, then f.e. standard R2R self-adhesive tag materials or flatbed media (PVC, PP, PS) is recommended(2) R&D on functional inkjet inks (focus: thermochromic and photochromic inks); if available then inkjet printing of those using the Durst Rho printer series

Product materials recyclability API (Europe) and Recycling locations API (on demand)

API Endpoints to obtain recycling information and disposal locations based on materials of products in Europe.

Page 13/13