Description of EU H2020 TagItSmart project and open call process

1. You Tag it; we fund it!
Using SmartTags and funding opportunities
Guildford IoT meetup, 17 October 2017
Stylianos Georgoulas, ICS, University of Surrey

2. What TagItSmart is about
• H2020 ICT30 project
• 1 January 2016 - 31 December 2018
• Part of IOT-EPI initiative
• 15 core partners
• 2 open calls so few more (8) have got / will get on board
• 1st open call selection finalized; 4 modules and 2 pilots/use cases accepted
• 1st Open Call projects started on 1st September 2017
• 2nd open call officially opened on 15th September 2017
2

3. What TagItSmart is really about
• Key concept
• SmartTags attached to products
• Functional inks or NFC-based
• Can react to light, temperature, humidity, time, other environmental conditions
• With end-user engagement you have a bunch of sensors on every day products
• What we want to do
• Give voice to mass products even at per item-level
• Exploit the pervasiveness of mobile phones; use them not only for Facebook or
watching Justin Bieber videos; use them as relays to a back-end
• Exploit stored scan data for service improvement and analytics
3

4. SmartTags in a nutshell
4

5. “In-house” use cases
• 5 industrial “in house” use cases identified so far driven by real-life interests of consortium
partners
• Digital Product
• Lifecycle Management/Recycling
• Brand Protection
• Dynamic Pricing
• Home Services
• All leverage the power of SmartTags
5

6. 1st Open Call use cases and modules
• Use cases
• Brand protection in wine distribution
• Condition tracking of health/hospital consumables (e.g. vaccines)
• Modules to extend TagItSmart platform
• Authentication based on social interaction detection
• Product freshness and dynamic best before date
• Post sales monitoring of home appliances
• Correlation of events from different verticals for event prediction/identification
• Use cases that consider different domains and have pilot facilities
• Modules of big interest to platform extension and use case needs
6

7. 2nd Open Call Facts
• Use cases and modules
• Use cases (150k - 9 months duration)
• Modules (50k - 5 months duration)
• Areas of particular interest: Industry 4.0, Blockchain, Artificial Intelligence,
Augmented Reality and context detection for service customization
• Important dates
• Deadline for submission 1st November 2017
• Notification of acceptance 15th December 2017
• Start date 1st February 2018
• Technical Part of proposal: 15 pages
7

8. Find out more
• www.tagitsmart.eu
• #TagItSmart (twitter)
• TagItSmart (LinkedIn group)
• ecosystem@tagitsmart.eu (will also be used for submission of Open Call proposals)
• info@tagitsmart.eu
• For any questions and more information regarding the 2nd Open Call
• helpdesk@tagitsmart.eu
• http://tagitsmart.eu/opencall
• A series of information moments (F2F) will be announced soon in the website
8

9. 1st Open Call Success Stories
• Let’s see what two 1st Open Call winners think of us
• About the process
• About the collaboration so far (from asking information prior to the submission, to
meeting us in person)
• About what value they see for their organization coming out of their Open Call
project
• MATISSE (eHealth), use case
• Therapenis and City Clinic (Athens)
• AffectUs (Multi-source event detection), module
• HUA (Athens)
9

10. Leveraging TagItSmart on eHealth
MATISSE+
Innovation Night, Athens, 27/09/2017

11. MATISSE: A beneficial synergy
Provides eHealth
services, on top of:
• IoT
• Cloud computing
• Big Data analytics
11
+STARTUP
Provides the
platform and tools
to realize smart
tagged IoT
Exploits TagItSmart on eHealth,
to minimize “never events”
through:
• real-time drugs/pills
lifetime/aptness verification
• medication administration
• real-time quality assessment
Research & Innovation

12. The MATISSE Journey
12
Proposal
Submission
OpenCall #1
Project
Start
MATISSE
meets
TagItSmart
Now
Project
End
MATISSE
into market
• Interface person
already assigned to
Matisse
• Smart tags already
received for
testing/development
• Professional and
effective
communication of
accompanying
information
• Soon after the
project started
• Eager
Consortium
• Great potential
through exploitation
of the TagItSmart
platform/services
• Great prospects for
a fruitful cooperation
• Consortium
responsiveness
minimizes
communication
overhead/delays &
creates chances for
improvements on
our solution
• TagItSmart
Consortium
comprises diverse
stakeholders
• Given MATISSE
experience, bi-
/multi-lateral
cooperation at
business level can
be mutually
beneficial

13. Multi-source event detection
AffectUs
Innovation Night, Athens, 27/09/2017

14. How to find the Open Call
• There are strategic initiatives that have a
dissemination goal for ongoing projects
• IoT-EPI
• http://iot-epi.eu/open-calls/
• This includes all current and future open calls
• Be sure to have registered to key channels that
offer information and reminders
• E.g. IERC mailing list
• ierc@internet-of-things-research.eu
• IoT-EPI twitter accounts
• RSS feeds from relevant websites if available
• Helps to ‘a-synchronize’ the process
14

15. Collaboration points
• Do consider getting familiar with the concepts and tools offered by the project
• Before or at the beginning of contemplating on the proposal
• Check templates and needed information
• Example: EVRYTHNG platform of TagItSmart
• Be sure to align your goals with the project’s to maximize interest, reduce integration and
fit in scope
• During proposal writing communication for clarifying questions on the scope, technical
and administrative issues
• TagItSmart always answered swiftly
15

16. Expectations from AffectUs side
• When we started the process
• Fast and to the point development of the proposal
• Short template, not too much time spent on the actual proposal text (Big Plus!!!!)
• Extremely large difference from going after a standard H2020 project call
• Focus only on the points of interest for us
• No need for the existence of a large team, established contacts etc.
• During the extension implementation
• Avoiding too much communication overhead
• Access to datasets for testing/research purposes
• Access to operational frameworks that cater for most of the background functionality,
enabling us to work only on our extension
• After finalization
• To have a working prototype
• Research papers (due to our scope)
• Potential further collaboration with the main collaborating partners
16

17. Thank you!
17