Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

2016 07-20-wp8-q2 f2 f berlin

Pilot Design, Execution and Evaluation

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all
  • Be the first to comment

2016 07-20-wp8-q2 f2 f berlin

  1. 1. WP8 Pilot Design, Execution & Evaluation LEADER: BIOASSIST INVOLVED PARTNERS: CREATENET, IMINDS, ATOS, JOLOCOM, UNI PASSAU, SKYWATCH, MOBISTAR, INRIA, EUROTECH AGILE MEETING, 20-21 July 2016, Berlin
  2. 2. WP8 – Timeline Active Tasks: ◦ T8.1 Design and Requirements Specification for Pilots (BIO) ◦ T8.2 Pilot Components Development & Integration (ATOS) 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) 20-21 April 2016 AGILE MEETING, BERLIN 2
  3. 3. •Scenario & Business View •Storyline & Use Cases •Users, Stakeholders & Roles •Requirements Identification Done •Requirements Analysis •Map Requirements to AGILE WPs and Tasks •KPIs •Pilot Architecture & Component Descriptions Ongoing •Mapping of Pilots' Architectures to AGILE Components •Administrative Procedures •Pilot Operation & Evaluation Methodologies •Implementation (T8.2) To-do Status 20-21 April 2016 AGILE MEETING, BERLIN 3
  4. 4. Use Cases Example 20-21 April 2016 AGILE MEETING, BERLIN 4
  5. 5. ID PA-1.2 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 Preconditions 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. Main Success Scenario 1. The actor enters the gateway’s IP address into a web browser and logs in with their credentials. 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. Extensions 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. Priority High 20-21 April 2016 AGILE MEETING, BERLIN 5
  6. 6. Requirements Example 20-21 April 2016 AGILE MEETING, BERLIN 6 Id PA_HW_1 Name BLE Communication Priority High Descri ption The AGILE Gateway must support BLE Communication (natively or via a shield) with sensors and devices. Type Hardwa re Sourc e PA-1.2 PA-2.1 Compo nent(s) AGILE Gateway (Makers’) Verifica tion Design Id PA_HW_2 Name WiFi Communication Priority High Descrip tion The AGILE Gateway must provide connection with home networks and internet via WiFi. The latest WiFi standards should be supported (802.11n). Type Hardware Source Overall Use Case Scenario Compon ent(s) AGILE Gateway (Makers’) Verificati on Design
  7. 7. Pilot A QuantifiedSelf • 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 WebIDs • 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
  8. 8. Open Issues Integrate with Smartwatches and Activity Trackers? When we can start using the AGILE components? 20-21 April 2016 AGILE MEETING, BERLIN 8 Pilot A
  9. 9. 20-21 April 2016 AGILE MEETING, BERLIN 9 Pilot B 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 Online/Offline modes ◦ 4G connection where available or ◦ Οff-line data storage and processing
  10. 10. Pilot B Open Field & Cattle Monitoring oRegulation and Flight permissions oGround Based Sensors Pilot B 20-21 April 2016 AGILE MEETING, BERLIN 10
  11. 11. Pilot C Air quality and pollution monitoring 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 SW
  12. 12. Pilot D 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 Services • Customized Promotions according to user profiles • The AGILE Gateway • Coordinates a network of iBeacons • Pushes notifications to the users’ smartphone apps • Improved shopping experience
  13. 13. Open Issues 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? http://www.eroski.es/ Pilot D 20-21 April 2016 AGILE MEETING, BERLIN 13
  14. 14. Pilot E Port Area Monitoring for Public Safety 20-21 April 2016 AGILE MEETING, BERLIN 14 • Crisis management using the AGILE Gateway on UAVs • 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 drone • Data transfer over 4G cellular networks • Streaming data: • Data from various sensors • Video Streaming
  15. 15. Open Issues 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 Pilot E
  16. 16. 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 download.
  17. 17. Open Issues §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 IoT Testbed 20-21 April 2016 AGILE MEETING, BERLIN 17
  18. 18. WP8 Next Steps – T8.1 Finalize Requirements Analysis ◦ Map Requirements to AGILE WPs and Tasks ◦ KPIs Pilot Architecture & Component Descriptions ◦ Mapping of Pilots' Architectures to AGILE Components Pilot Operation & Evaluation Methodologies ◦ Administrative Procedures ◦ User Recruitment ◦ Locations 20-21 April 2016 AGILE MEETING, BERLIN 18
  19. 19. 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 leader 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 packages 20-21 April 2016 AGILE MEETING, BERLIN 19
  20. 20. D8.1 ToC Introduction Overall Approach and Methodology Pilots (Content from Google Documents) ◦ Storyline ◦ Users, roles etc. ◦ Use Cases ◦ … IoT Testbed Requirements Analysis Pilot Architecture Pilot Operation / Milestones / Timeline Conclusion 20-21 April 2016 AGILE MEETING, BERLIN 20
  21. 21. Thank you! 20-21 April 2016 AGILE MEETING, BERLIN 21

    Be the first to comment

    Login to see the comments

  • PabloGustavoTiburcio

    Dec. 19, 2016

Pilot Design, Execution and Evaluation

Views

Total views

466

On Slideshare

0

From embeds

0

Number of embeds

0

Actions

Downloads

8

Shares

0

Comments

0

Likes

1

×