Raffaele Giaffreda / FBK CREATE-NET Project Coordinator

1. AGILE M18 Review, 20 October 2017, Brussels (Belgium)
AGILE M18 – State of the “Nation”
RAFFAELE GIAFFREDA / FBK CREATE-NET
PROJECT COORDINATOR
1

2. Brief introduction to AGILE Review
Main achievements
Agenda
Timeline
2

3. MAIN ACHIEVEMENTS

4. AGILE Main Achievements
4
Hardware
◦ Industrial + Makers
◦ Interoperability, modularity
Software
◦ Mgmt of: device + protocol
+ data + storage
◦ Modularity (micro-services)
◦ Integration into Node-Red
GUI for Rapid prototyping
AGILE
Modularity
Extensibility
Device & Data
Management
IoT Apps
Ecosystem
Workflow
recommendation
Community Engagement &
Exploitation
Graphical App
Development
Diverse Pilots
Privacy - Data
Provenance
External Clouds
AGILE Testbed
AGILE OBJECTIVES

5. AGENDA

6. Agenda
6
14.00 restart
14.00 (90min) AGILE Pilots — (BIOASSIST +
Pilot leaders) (WP8)
15.30 (20min) innovations radar — (IMEC)
15.50 (10min) Coffee Break
16.00 (20min) impact, open calls and
external collaboration — (IMEC)
16.20 (20min) partnership and
dissemination — (Eclipse)
16.40 (30min) Administrative / financial —
(FBK)
17.10 (35min) reviewers / PO debriefing
17.45 (15min) PO to present main
conclusions / first feedback
18.00 end
9.00 Start
(15min) Brief intro (FBK)
9.15 (30min) IoT Hardware innovation —
(Eurotech)
9.45 (45min) Enabling rapid prototyping
(Rulemotion, FBK)
10.30 (15min) Coffee Break
10.45 (20min) AGILE Development
Environment, demo — (FBK)
11.05 (30min) AGILE Research, (TU Graz,
PASSAU)
11.35 (40min) IoT and Cloud services —
(ATOS)
12.15 (15min) Q&A
12.30 Lunch

7. WORK-PACKAGE MAPPING

8. Mapping the Agenda to AGILE
overall Work-Package structure
8
Hardware
innovation
Enabling
rapid
prototyping
AGILE Developers
Environment
AGILE
Research
IoT and Cloud
Services
AGILE Pilots

9. ARCHITECTURE MAPPING

10. Mapping to AGILE Architecture –
Development View
10

11. 11
Web-level APIs
AGILE Cloud Services (Xively,
Dropbox, OwnCloud etc.)
low-level
components
Containers
Gateway OS

12. TIMELINE

13. Where are we?
13
Maintenance
Integration
(streamlining)

14. Canonical Replacement
14
1. On the technical front we need more resources to:
t.a.1 — tackle outstanding build issues (e.g. automate ARM build of Java based docker images)
t.a.2 — Improve QA by implementing automated testing (both component and AGILE stack level)
t.a.3 — Identify and resolve performance bottlenecks
t.a.4 — Provide resources to resolve software related issues (prioritized by a project level taskforce)
— Fix high priority software bugs— Implement “worthy” improvements (request from project
partners, or from external users such as open call winners)
t.a.5 — Provide technical support to AGILE users (open call winners, other users)
t.a.6 — Improve the quality and/or the attractiveness of the AGILE development environment
(implement protocols, implement "catchy" device support, etc.)
2. dissemination
d.a.1— Dissemination activities which, while not foreseen in the current DoA, could enhance the
exploitation of the AGILE project results.
3. security
s.a.1 — Handling lack of expected Canonical contribution to the Security work-package
Project Status Assessment

15. THANK YOU