WP8 Pilot Design, Execution & Evaluation

WP8
Pilot Design, Execution & Evaluation
LEADER: BIOASSIST
INVOLVED PARTNERS:
CREATENET, IMINDS, ATOS, JOLOCOM, UNI PASSAU, SKYWATCH,
MOBISTAR, INRIA, EUROTECH
AGILE MEETING, 14-15 April 2016, Athens

WP8 – Timeline
Milestones:
◦ MS1 (M9) - AGILE Initial Design & Draft Framework Release
◦ MS2 (M18) - MS2 AGILE Framework (SW and HW) release & Initial Integration
◦ MS5 (M36) - Final Project Outcome & Exploitation Report
Deliverables:
◦ D8.1 Pilot Design and analysis requirements and specification (M9)
◦ D8.2 Initial Pilot Components Development & Deployment Report (M18)
◦ D8.3 Final Pilot Deployment & Evaluation Report (M36)
14-15 April 2016 AGILE MEETING, ATHENS 2

• Scenario Overview
• Business View
• Scenario Rationale
• Storyline
• Users, Stakeholders and
Roles
Done
• HW Specifications
• Data Aspects
• Communication
Technologies and Protocols
• External Cloud Endpoints /
Services
• Security and Privacy
• Risks
Ongoing • Use Cases
• Pilot Architecture and
Component Descriptions
• Requirements Definition
• Administrative procedures
• KPIs
To-do
Status
Definition of the scenarios and IoT Testbed
5 + 1 shared documents which will be the basis for D8.1

WP8 Next Steps
Synchronize requirements’ specification with the other WPs
Define of Use Cases / Diagrams
Design the components and overall architecture of each pilot
Identify KPIs
Development of plan for pilot preparation / operation / evaluation
◦ User Recruitment
◦ Locations
Development of the overall methodology for WP8 for the pilots

Hardware Requirements
Makers Version
Pilot A Pilot D Pilot B Pilot E
BLE Weight / Volume / Power
WiFi WiFi / 3G/4G 3G/4G
Display Status GPS
Data Visualization Compatible with sensors:
1)Stationary sensors (Libelium)*
2)Eartag sensors for animals
(Fastcom)
Swappable sensor
modules for shields:
1) multigas
2) radiation
Connection with
HD/infrared camera
Connect to the controller
of the drone proxy
MAVLink messages.

Hardware Requirements
Industrial version
◦ Modularity for sensing and connectivity.
◦ Support for multiple WAN/LAN connectivity options.
◦ Support for a wide range of environmental sensing modules.
◦ with pre-calibrated sensor conditioning.
◦ Timestamp and optional geo-localization information.
◦ Fanless thermal design.
◦ Maximum power consumption 5W.
◦ Extended temperature range support (target -20 +70 °C).
◦ Small , highly integrated.
◦ Maximum size: board 180 x 100 x 50 mm (LxDxH).

Pilot A
QuantifiedSelf

Requirements
Hardware
◦ BLE Communication
◦ Display status / data visualization
Data
◦ Handle different types of data and sources
◦ e.g. biosignal sensors / smartwatches
◦ Cloud platforms / services from application providers are data sources
◦ e.g. Misfit, GoogleFit
◦ Basic processing on the gateway, advanced processing on the Cloud
◦ build the user profile and identify trends, risks etc.
◦ Data sharing of raw and processed data with other users
◦ Friends, Relatives, Healthcare experts
Security
◦ User in control of
◦ what to share
◦ with who,
◦ when (adhoc/ automatically / periodically)
Pilot A

Open Issues
Data sharing process
◦ Consider data types / APIs
◦ Specifications (Open mHealth)
◦ Share to apps / platforms
◦ Ongoing discussions with Jolocom
Direct communication of smartwatches / activity trackers with the
gateway
◦ Typically done through cloud services
Use of TU Graz recommenders?
Pilot A

Next Steps
Detailed analysis, categorization and specification of the pilot
requirements
Define of Use Cases / Diagrams
Design the pilot components and overall architecture
Identify KPIs
Development of plan for pilot preparation / operation / evaluation
◦ User Recruitment
◦ Locations
Pilot A

Pilot B
Open Field & Cattle Monitoring
Dynamic IoT Sensor
Use Case
Stationary IoT Sensor
Use Case

Use Cases: Win/Android
Example of User-Interface Dynamic IoT Sensors on animals Stationary IoT Sensors on the ground
Pilot B

Requirements (1/2)
Hardware requirements :
◦ Agile Gateway (Makers)
◦ Stationary sensors (Libelium)*
◦ Eartag sensors for animals (Fastcom)
◦ Own Hardware
◦ Cumulus
◦ Huginn
◦ Windows tablet
Pilot B

Requirements (2/2)
Software requirements:
◦ API for Data Presentation (GUI)
◦ VPN Tunnelling
Security requirements
◦ Encrypted data link
◦ Encrypted onboard storage
◦ Data should be accessible trough an authenticated cloud service
Pilot B

Pilot 1: Stationary Sensor
◦ Pilot 2b – Eye in the Sky
◦ Based on Water samples detection of mining activities in the
rain forest
Pilot B

Pilot 2: Dynamic Sensor
◦ Pilot 2a – Hofmansgave Gods
◦ 7 acres
◦ 50+ Cows
◦ Pilot 2b – Karen Blixen Camp
◦ 100 + animals
◦ Elephants, Rhinos, Cattle
◦ 30.000 acre area
◦ Support from national conservatory
◦ Mara North 60.000 animals
Pilot B

Open Issues
o Regulation and Flight permissions
o Ground Based Sensors
Pilot B

Next Steps
o Get signed Letter of Intents from Pilot Partners
o More detailed project plan for availability of Gateway for integration
o Roll out plan for Pilots
Pilot B

Pilot C
Air quality and pollution monitoring

Requirements (Preliminary)
based on the industrial version of the modular gateway
◦ Modularity for sensing and connectivity.
◦ Support for multiple WAN/LAN connectivity options.
◦ Support for a wide range of environmental sensing modules.
◦ with pre-calibrated sensor conditioning.
◦ Timestamp and optional geo-localization information.
◦ Fanless thermal design.
◦ Maximum power consumption 5W.
◦ Extended temperature range support (target -20 +70 °C).
◦ Small , highly integrated.
◦ Maximum size: board 180 x 100 x 50 mm (LxDxH).
Pilot C

Software Requirements
◦ Yocto Linux
◦ Kura
◦ Kura Wires
◦ Everyware Cloud
◦ Eclipse OSGi Equinox
◦ Eclipse Paho
◦ Red Hat JBoss
◦ Apache Camel
◦ HyperSQL
Protocol:
◦ MQTTS
Pilot C

Open Issues and Next Steps
Open issues
◦ Scenario still to be confirmed.
◦ New meeting planned for 20 of April.
Next steps
◦ Consolidate the scenarios,
◦ define the use cases and
◦ …finalize the Pilot description.
Pilot C

Pilot D
Enhanced Retail Services

Requirements (1/3)
Hardware requirements:
◦ Agile Gateway
◦ Raspberry Pi 3 model B for Beacon smart network
https://www.raspberrypi.org/products/raspberry-pi-3-
model-b/
◦ Kontakt beacons https://kontakt.io/
◦ Wireless smart button for feedback without smartphone
https://flic.io/
◦ Android Samsung S6 or newer smartphone
◦ Cloud retailer services deployed on Amazon AWS
Pilot D

Requirements (2/3)
Software requirements:
◦ Node.js on Raspberry Pi nodes.
◦ Docker with snappy for apps deployed on AGILE Gateway.
◦ JEE for the services deployed on Amazon AWS.
◦ AngularJS on Backoffice user interface.
◦ Ionic on smartphone customer application.
◦ MongoDB on retailer server storage.
Pilot D

Requirements (3/3)
◦ We only manage anonymous data from customers at our tracking system.
◦ Users’ personal information can only be accessed through apps using HTTPS and
authentication and authorization mechanisms based on OAuth2.
◦ Backoffice accesses data using the same security system than mobile app is using.
◦ Nobody can access data in Gateways. It’s the Gateway itself who sends its data to
external systems. It will also perform polling in configuration and notification
tasks to IoT devices during the Pilot.
Protocols and communications
◦ System uses HTTPS for all communications between nodes.
◦ Nodes will use certificates in order to create a trust network between servers and
avoiding this way man-in-the-middle attacks.
Pilot D

Use Case: Snappy
Functional Snappy Modules:
◦ Smart iBeacon network (mandatory). Network manager iBeacons / Raspberries
that monitors the status of all nodes and the information they generate when
they detect the beacons associated to components subject to monitoring
◦ Employee tracker. Identification and monitoring of employees associated
iBeacons.
◦ Customer tracker. Identification and monitoring of shopping carts associated
iBeacons .
◦ Customer Queues listener. Receiver to measure the waiting time for the Ibeacons
shopping carts.
◦ Customer Feedback listener. Receiver Module of Smart buttons Feedback.
◦ Retailer Feedback notification listener. Indoor module to push notifications
feedbacks received by smart buttons or external servers.
Pilot D

Use Case: Android App
Main use cases:
◦ Welcome notification.
◦ Indoor location shopping list.
◦ Indoor location Promotion or suggestions.
◦ Where I am?
◦ Information points (Near or absolute location.
◦ Cashier status.
◦ Feedback.
Pilot D

Open Issues
oSet up and test the device network
oTo confirm the Retailer to operate the pilot. Eroski?
http://www.eroski.es/
Pilot D

Next Steps
o Define in deep detail the Use cases for the Agile Gateway
o Define in deep detail the Business Use Cases of the Retailer
functionality
oDefine the objectives and KPI’s to assess the Pilot impact
oTechnology assessment of the pilot scenario (Setup and Test a
prototype)
oFollow up Agile Gateway evolution (capabilities, functionality…)
oConfirm the Retailer
oDefine a project timeline and project plan for the Pilot
Pilot D

Pilot E
Port Area Monitoring for Public Safety
• Sensors on the drone will capture the
information and send it over 4G towards
the application via the gateway.
• Users can view the data via the
application.
• With the application users can send
requests to the drone over 4G via the
gateway
Pilot E

Requirements
Hardware requirements agile gateway
• Communication should be done via 3G/4G.
• Sensor modules should be swappable (wireless or
connection bay).
• Connect to the controller of the drone proxy MAVLink
messages.
• Connection with HD camera.
• Connection with infrared camera.
• Connection to the multigas sensor shield
• Connection to the radiation shield
Pilot E

Requirements
Hardware requirements drones final product
• Carriage load:
• Minimum safe flight time:
• Speed:
• Max range:
> 1kg
35 min
> 60km/h
20km
Pilot E

Requirements
Data management
• Store camera images and sensor data on gateway when
4G is not available.
• No user data is transmitted via the gateway.
• Data cannot be accessed by users directly on the gateway.
• Data only available via API’s for instances which are
allowed to consult the data.
Pilot E

Requirements
• Data will only be available through RESTful API’s for a
selected number of applications.
• Users can only access data via the application, and only
data which they have access to.
Pilot E

Open Issues
• Drone requirements do not match drone specifications.
• It is good enough for a proof of concept, but not for a final product.
• Not yet clear where Belgian legislation stands at the
moment.
• Not clear which budget to use for the hardware.
Pilot E

Next Steps
• Describe the different use cases in detail
• Define the objectives and KPI’s.
• Determine test site.
• Discuss the drone requirements.
Pilot E

IoT Testbed
§ HW and SW Infrastructure already in place for remote, bare-metal
access to 2700+ IoT-devices.
§ Online tools for IoT node firmware upload, experiment configuration,
experiment results download.

Planned Testbed Extension
USB plugged-in AGILE gateway hardware on IoT-LAB host A8-M3 nodes
Blue: userland
Yellow: admin
Green: userland extension
IoT Testbed

Requirements
SW: the testbed offers bare-metal access to IoT devices, so there is no SW
requirements on IoT devices. No specific req. on AGILE gateway SW either
(except: must be able to run on AGILE hardware e.g. RasPi)
HW: IoT devices are currently IEEE 802.15.4 only on the targeted IoT-LAB
site => AGILE gateway should have a IEEE 802.15.4 communication module
(which may be a USB-connected board running RIOT).
Security requirements:
◦ ssh tunnel to AGILE gateway, where AGILE interfaces can be used (and
corresponding security considerations apply).
◦ Bare-metal access to IoT-devices: e.g. RIOT firmware running on IoT-LAB M3
nodes, with IPv6/6LoWPAN/RPL/UDP stack (and corresponding security
considerations apply).
Data management, post-processing and visualization: up to the testbed
users. Out of scope for the testbed tools. Pre-processing possible on the IoT-
devices (programmable in the firmware uploaded on IoT devices e.g. RIOT)
IoT Testbed

Open Issues
Framework to avoid user-initiated file-system «bricking» on the gateway
◦ Based on NFS boot?
Final decision between several possible levels of integration:
◦ Level 1: adding new IoT devices to IoT-LAB (connecting them through USB to
one of the A8-M3 nodes)
◦ Level 2: adding new gateways to IoT-LAB (e.g. AGILE gateway)
◦ connecting via an existing Open A8 - maybe USB-Ethernet
◦ connecting to the private Ethernet of IoT-LAB local serve
◦ alternative: connect via an additional private server, with an admin VM dedicated to AGILE.
◦ Level 3: modifying SW (currently a customized OpenEmbedded - Yocto Daisy)
on IoT-Lab A8 nodes so that they become an AGILE Gateway, e.g. using
Snappy
IoT Testbed

Next Steps
§ Plug in AGILE hardware (maker version): RasPi + 802.15.4 module
§ Auto-configuration of global IPv6 addresses on AGILE gateway
IoT Testbed

Thank you!

WP8 Pilot Design, Execution & Evaluation

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (14)

Similar to WP8 Pilot Design, Execution & Evaluation

Similar to WP8 Pilot Design, Execution & Evaluation (20)

More from AGILE IoT

More from AGILE IoT (9)

Recently uploaded

Recently uploaded (20)

WP8 Pilot Design, Execution & Evaluation