Pilot Design, Execution & Evaluation
CREATENET, IMINDS, ATOS, JOLOCOM, UNI PASSAU, SKYWATCH,
MOBISTAR, INRIA, EUROTECH
AGILE MEETING, 20-21 July 2016, Berlin
WP8 – Timeline
◦ T8.1 Design and Requirements Specification for Pilots (BIO)
◦ T8.2 Pilot Components Development & Integration (ATOS)
◦ 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)
20-21 April 2016 AGILE MEETING, BERLIN 2
•Scenario & Business View
•Storyline & Use Cases
•Users, Stakeholders & Roles
•Map Requirements to
AGILE WPs and Tasks
•Pilot Architecture &
Ongoing •Mapping of Pilots'
Architectures to AGILE
•Pilot Operation &
20-21 April 2016 AGILE MEETING, BERLIN 3
Use Cases Example
20-21 April 2016 AGILE MEETING, BERLIN 4
Title Manage Sensors
Description The actor logs in to the gateway’s interface to pair a sensor with the AGILE Gateway.
Actor(s) AGILE User
The AGILE Gateway is connected to the home WiFi network.
The Bluetooth interface of the AGILE Gateway is on.
In order to pair a sensor, the device must be within the range of the AGILE Gateway.
Postconditions The list of paired devices and the corresponding settings are updated.
1. The actor enters the gateway’s IP address into a web browser and logs in with their
2. The actor selects the ‘Device Management’ UI. The list of paired sensors is displayed.
3. The actor turns on the sensor.
4. The AGILE Gateway automatically discovers the sensor, which is added to the list.
5. The actor pairs the devices, if needed.
3a. The actor selects a device from the list
--- 3a1. The AGILE Gateway displays the device settings panel.
--- 3a2. The actor configures the device settings.
3b. The actor selects a device and deletes it from the list.
4a. The AGILE Gateway cannot discover the device.
--- 4a1. The actor either backs out of this use case or tries again.
5a. There is an error during the pairing of the devices.
--- 5a1. The AGILE Gateway displays an error message.
--- 5a2. The actor either backs out of this use case or tries again.
20-21 April 2016 AGILE MEETING, BERLIN 5
20-21 April 2016 AGILE MEETING, BERLIN 6
Id PA_HW_1 Name BLE
The AGILE Gateway must support BLE
Communication (natively or via a shield) with
sensors and devices.
Id PA_HW_2 Name WiFi
The AGILE Gateway must provide connection
with home networks and internet via WiFi. The
latest WiFi standards should be supported
Source Overall Use
• Home / Daily use by non-experts
• Auto-configuration support
• Data Security and Privacy
• AGILE Security Framework with policy
configuration and enforcement
• Data Sharing
• A data sharing framework based on
• Import data from 3rd parties
• Data Analysis in the gateway
• Identification of trends
• Update user’s activity profile
20-21 April 2016 AGILE MEETING, BERLIN 7
Integrate with Smartwatches and Activity Trackers?
When we can start using the AGILE components?
20-21 April 2016 AGILE MEETING, BERLIN 8
20-21 April 2016 AGILE MEETING, BERLIN 9
Open Field & Cattle Monitoring
AGILE Gateway on UAVs for monitoring
open/remote areas and livestock
◦ Payload and power consumption restrictions
Integration with the UAV control systems
◦ 4G connection where available or
◦ Οff-line data storage and processing
Open Field & Cattle Monitoring
oRegulation and Flight permissions
oGround Based Sensors
20-21 April 2016 AGILE MEETING, BERLIN 10
Air quality and pollution
20-21 April 2016 AGILE MEETING, BERLIN 11
• A pervasive network of AGILE
Gateways as monitoring stations
• Use of the industrial version
• reduce the cost
• reduce the time to market
• create business opportunities
• Modular HW Design
• Sensing Modules
• Networking Modules
• Auto-configuration of modules and
Enhanced Retail Services
20-21 April 2016 AGILE MEETING, BERLIN 12
• Transform the future consumer
behavior and provide retailers
with new opportunities
• Proximity and Location Based
• Customized Promotions according
to user profiles
• The AGILE Gateway
• Coordinates a network of
• Pushes notifications to the users’
• Improved shopping experience
Initial tests with the Raspberry Pi 3 Model B and kontak.io beacons.
To confirm the Retailer to operate the pilot and the locations. Eroski?
20-21 April 2016 AGILE MEETING, BERLIN 13
Port Area Monitoring for Public
20-21 April 2016 AGILE MEETING, BERLIN 14
• Crisis management using the AGILE Gateway
• A trigger will be sent to a drone to fly out to the
coordinates of an incident and will be
transmitted in real time
• The data will be collected by Sky-Watch drones
carrying the AGILE gateway
• Allow the control room to have control over the
• Data transfer over 4G cellular networks
• Streaming data:
• Data from various sensors
• Video Streaming
Currently in discussions with 2 drone builders to provide drones.
Legislations: there is an update for Belgium, the legislation is very strict,
however for our project it shouldn't be an issue since flights will be
authorized by the necessary authorities.
Location: we are currently in discussion with the city to use one of the
sites in the harbor. I don't have a status yet.
Questions: When can we use a gateway? How can we get it? How can
we get sensors? Do we need to order it? Which budget will cover this?
20-21 April 2016 AGILE MEETING, BERLIN 15
Testbed Overview: IoT-LAB
20-21 April 2016 AGILE MEETING, BERLIN 16
§ To be used as pre-pilot in order to decrease debugging phase of the AGILE pilots
§ 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
§Industrial gateway vs. Maker gateway (and how many ?)
§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 server
◦ 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
20-21 April 2016 AGILE MEETING, BERLIN 17
WP8 Next Steps – T8.1
Finalize Requirements Analysis
◦ Map Requirements to AGILE WPs and Tasks
Pilot Architecture & Component Descriptions
◦ Mapping of Pilots' Architectures to AGILE Components
Pilot Operation & Evaluation Methodologies
◦ Administrative Procedures
◦ User Recruitment
20-21 April 2016 AGILE MEETING, BERLIN 18
WP8 Next Steps – T8.2
Start: M7 (July‘16), End: M18 (June‘17) (already started!!)
Each pilot is responsible for its own development, task
leader (Worldline) to monitor progress, together with WP8
Monitoring through short and focused regular
teleconferences, frequency and date to be agreed
First teleconference to take place immediately after holidays
period, date to be agreed
Objective: work plan for each pilot, set deadlines, follow-up,
identify potential problems, give feedback to other work
20-21 April 2016 AGILE MEETING, BERLIN 19
Overall Approach and Methodology
Pilots (Content from Google Documents)
◦ Users, roles etc.
◦ Use Cases
Pilot Operation / Milestones / Timeline
20-21 April 2016 AGILE MEETING, BERLIN 20
20-21 April 2016 AGILE MEETING, BERLIN 21