2016 07-20-wp8-q2 f2 f berlin
Transcript of 2016 07-20-wp8-q2 f2 f berlin
![Page 1: 2016 07-20-wp8-q2 f2 f berlin](https://reader031.fdocuments.net/reader031/viewer/2022030304/587a9cbc1a28ab09758b6209/html5/thumbnails/1.jpg)
WP8PilotDesign,Execution&EvaluationLEADER: B IOASS IST
INVOLVED PARTNERS : CREATENET, IMINDS , ATOS , JOLOCOM, UNI PASSAU, SKYWATCH, MOBISTAR , INR IA , EUROTECH
AGILEMEETING,20-21July2016,Berlin
![Page 2: 2016 07-20-wp8-q2 f2 f berlin](https://reader031.fdocuments.net/reader031/viewer/2022030304/587a9cbc1a28ab09758b6209/html5/thumbnails/2.jpg)
WP8– Timeline
ActiveTasks:◦ T8.1DesignandRequirementsSpecificationforPilots(BIO)◦ T8.2PilotComponentsDevelopment&Integration(ATOS)
Deliverables:◦ D8.1PilotDesignandanalysisrequirementsandspecification(M9)◦ D8.2InitialPilotComponentsDevelopment&DeploymentReport(M18)◦ D8.3FinalPilotDeployment&EvaluationReport(M36)
20-21April2016 AGILEMEETING,BERLIN 2
![Page 3: 2016 07-20-wp8-q2 f2 f berlin](https://reader031.fdocuments.net/reader031/viewer/2022030304/587a9cbc1a28ab09758b6209/html5/thumbnails/3.jpg)
• Scenario&BusinessView•Storyline&UseCases•Users,Stakeholders&Roles•RequirementsIdentification
Done
•RequirementsAnalysis•MapRequirementstoAGILEWPsandTasks
•KPIs• PilotArchitecture&ComponentDescriptions
Ongoing•MappingofPilots'ArchitecturestoAGILEComponents
•AdministrativeProcedures•PilotOperation&EvaluationMethodologies
• Implementation(T8.2)
To-do
Status
20-21April2016 AGILEMEETING,BERLIN 3
![Page 4: 2016 07-20-wp8-q2 f2 f berlin](https://reader031.fdocuments.net/reader031/viewer/2022030304/587a9cbc1a28ab09758b6209/html5/thumbnails/4.jpg)
UseCasesExample
20-21April2016 AGILEMEETING,BERLIN 4
![Page 5: 2016 07-20-wp8-q2 f2 f berlin](https://reader031.fdocuments.net/reader031/viewer/2022030304/587a9cbc1a28ab09758b6209/html5/thumbnails/5.jpg)
ID PA-1.2Title Manage SensorsDescription The actor logs in to the gateway’s interface to pair a sensor with the AGILE Gateway.
Actor(s) AGILE UserPreconditions
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-21April2016 AGILEMEETING,BERLIN 5
![Page 6: 2016 07-20-wp8-q2 f2 f berlin](https://reader031.fdocuments.net/reader031/viewer/2022030304/587a9cbc1a28ab09758b6209/html5/thumbnails/6.jpg)
RequirementsExample
20-21April2016 AGILEMEETING,BERLIN 6
Id PA_HW_1 Name BLE Communication
Priority High
Description
The AGILE Gateway must support BLE Communication (natively or via a shield) with sensors and devices.
Type Hardware
Source
PA-1.2PA-2.1
Component(s)
AGILE Gateway (Makers’)
Verification
Design
Id PA_HW_2 Name WiFi Communication
Priority High
Description
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
Component(s)
AGILE Gateway (Makers’)
Verification
Design
![Page 7: 2016 07-20-wp8-q2 f2 f berlin](https://reader031.fdocuments.net/reader031/viewer/2022030304/587a9cbc1a28ab09758b6209/html5/thumbnails/7.jpg)
PilotAQuantifiedSelf
• Home/Dailyusebynon-experts• Auto-configurationsupport
• DataSecurityandPrivacy• AGILESecurityFrameworkwithpolicy
configurationandenforcement
• DataSharing• Adatasharingframeworkbasedon
WebIDs• Importdatafrom3rd parties
• DataAnalysisinthegateway• Identificationoftrends• Updateuser’sactivityprofile
20-21April2016 AGILEMEETING,BERLIN 7
![Page 8: 2016 07-20-wp8-q2 f2 f berlin](https://reader031.fdocuments.net/reader031/viewer/2022030304/587a9cbc1a28ab09758b6209/html5/thumbnails/8.jpg)
OpenIssuesIntegratewithSmartwatchesandActivityTrackers?
WhenwecanstartusingtheAGILEcomponents?
20-21April2016 AGILEMEETING,BERLIN 8
PilotA
![Page 9: 2016 07-20-wp8-q2 f2 f berlin](https://reader031.fdocuments.net/reader031/viewer/2022030304/587a9cbc1a28ab09758b6209/html5/thumbnails/9.jpg)
20-21April2016 AGILEMEETING,BERLIN 9
PilotBOpenField&CattleMonitoring
AGILEGatewayonUAVsformonitoringopen/remoteareasandlivestock◦ Payloadandpowerconsumptionrestrictions
IntegrationwiththeUAVcontrolsystems
Online/Offlinemodes◦ 4Gconnectionwhereavailableor◦ Οff-linedatastorageandprocessing
![Page 10: 2016 07-20-wp8-q2 f2 f berlin](https://reader031.fdocuments.net/reader031/viewer/2022030304/587a9cbc1a28ab09758b6209/html5/thumbnails/10.jpg)
PilotBOpenField&CattleMonitoringoRegulationandFlightpermissions
oGroundBasedSensors
PilotB
20-21April2016 AGILEMEETING,BERLIN 10
![Page 11: 2016 07-20-wp8-q2 f2 f berlin](https://reader031.fdocuments.net/reader031/viewer/2022030304/587a9cbc1a28ab09758b6209/html5/thumbnails/11.jpg)
PilotCAirqualityandpollutionmonitoring
20-21April2016 AGILEMEETING,BERLIN 11
• ApervasivenetworkofAGILEGatewaysasmonitoringstations
• Useoftheindustrialversion• reducethecost• reducethetimetomarket• createbusinessopportunities
• ModularHWDesign• SensingModules• NetworkingModules• Auto-configurationofmodulesand
SW
![Page 12: 2016 07-20-wp8-q2 f2 f berlin](https://reader031.fdocuments.net/reader031/viewer/2022030304/587a9cbc1a28ab09758b6209/html5/thumbnails/12.jpg)
PilotDEnhancedRetailServices
20-21April2016 AGILEMEETING,BERLIN 12
• Transformthefutureconsumerbehaviorandprovideretailerswithnewopportunities
• ProximityandLocationBasedServices
• CustomizedPromotionsaccordingtouserprofiles
• TheAGILEGateway• Coordinatesanetworkof
iBeacons• Pushesnotificationstotheusers’
smartphoneapps• Improvedshoppingexperience
![Page 13: 2016 07-20-wp8-q2 f2 f berlin](https://reader031.fdocuments.net/reader031/viewer/2022030304/587a9cbc1a28ab09758b6209/html5/thumbnails/13.jpg)
OpenIssuesInitialtestswiththeRaspberryPi3ModelBand kontak.io beacons.
ToconfirmtheRetailertooperatethepilotandthelocations.Eroski?http://www.eroski.es/
PilotD
20-21April2016 AGILEMEETING,BERLIN 13
![Page 14: 2016 07-20-wp8-q2 f2 f berlin](https://reader031.fdocuments.net/reader031/viewer/2022030304/587a9cbc1a28ab09758b6209/html5/thumbnails/14.jpg)
PilotEPortAreaMonitoringforPublicSafety
20-21April2016 AGILEMEETING,BERLIN 14
• CrisismanagementusingtheAGILEGatewayonUAVs
• Atriggerwillbesenttoadronetoflyouttothecoordinatesofanincidentandwillbetransmittedinrealtime
• ThedatawillbecollectedbySky-WatchdronescarryingtheAGILEgateway
• Allowthecontrolroomtohavecontroloverthedrone
• Datatransferover4Gcellularnetworks• Streamingdata:
• Datafromvarioussensors• VideoStreaming
![Page 15: 2016 07-20-wp8-q2 f2 f berlin](https://reader031.fdocuments.net/reader031/viewer/2022030304/587a9cbc1a28ab09758b6209/html5/thumbnails/15.jpg)
OpenIssuesCurrentlyindiscussionswith2dronebuilderstoprovidedrones.
Legislations:thereisanupdateforBelgium,thelegislationisverystrict,howeverforourprojectitshouldn'tbeanissuesinceflightswillbeauthorizedbythenecessaryauthorities.
Location:wearecurrentlyindiscussionwiththecitytouseoneofthesitesintheharbor.Idon'thaveastatusyet.
Questions:Whencanweuseagateway?Howcanwegetit?Howcanwegetsensors?Doweneedtoorderit?Whichbudgetwillcoverthis?
20-21April2016 AGILEMEETING,BERLIN 15
PilotE
![Page 16: 2016 07-20-wp8-q2 f2 f berlin](https://reader031.fdocuments.net/reader031/viewer/2022030304/587a9cbc1a28ab09758b6209/html5/thumbnails/16.jpg)
TestbedOverview:IoT-LAB
20-21April2016 AGILEMEETING,BERLIN 16
§ Tobeusedaspre-pilotinordertodecreasedebuggingphaseoftheAGILEpilots§ HWandSWInfrastructurealreadyinplaceforremote,bare-metalaccessto2700+IoT-devices.§ OnlinetoolsforIoTnodefirmwareupload,experimentconfiguration,experimentresults
download.
![Page 17: 2016 07-20-wp8-q2 f2 f berlin](https://reader031.fdocuments.net/reader031/viewer/2022030304/587a9cbc1a28ab09758b6209/html5/thumbnails/17.jpg)
OpenIssues§Industrialgatewayvs.Makergateway(andhowmany?)
§Frameworktoavoid user-initiated file-system«bricking» onthegateway§ BasedonNFSboot?
§Finaldecisionbetweenseveralpossiblelevelsofintegration:§ Level 1:adding newIoT devices toIoT-LAB(connecting them through USBtooneoftheA8-M3nodes)
§ Level 2:adding newgateways toIoT-LAB(e.g.AGILEgateway)◦ connecting viaanexisting OpenA8- maybe USB-Ethernet◦ connecting totheprivate EthernetofIoT-LABlocalserver◦ alternative:connect viaanadditional private server,with anadminVMdedicated toAGILE.
§ Level 3:modifying SW(currently acustomized OpenEmbedded - Yocto Daisy)onIoT-Lab A8nodes so that they become anAGILEGateway,e.g.using Snappy
IoTTestbed
20-21April2016 AGILEMEETING,BERLIN 17
![Page 18: 2016 07-20-wp8-q2 f2 f berlin](https://reader031.fdocuments.net/reader031/viewer/2022030304/587a9cbc1a28ab09758b6209/html5/thumbnails/18.jpg)
WP8NextSteps– T8.1FinalizeRequirementsAnalysis◦ MapRequirementstoAGILEWPsandTasks◦ KPIs
PilotArchitecture&ComponentDescriptions◦ MappingofPilots'ArchitecturestoAGILEComponents
PilotOperation&EvaluationMethodologies◦ AdministrativeProcedures◦ UserRecruitment◦ Locations
20-21April2016 AGILEMEETING,BERLIN 18
![Page 19: 2016 07-20-wp8-q2 f2 f berlin](https://reader031.fdocuments.net/reader031/viewer/2022030304/587a9cbc1a28ab09758b6209/html5/thumbnails/19.jpg)
WP8NextSteps– T8.2Start:M7(July‘16),End:M18(June‘17)(alreadystarted!!)Eachpilotisresponsibleforitsowndevelopment,taskleader(Worldline)tomonitorprogress,togetherwithWP8leaderMonitoringthroughshortandfocusedregularteleconferences,frequencyanddatetobeagreedFirstteleconferencetotakeplaceimmediatelyafterholidaysperiod,datetobeagreedObjective:workplanforeachpilot,setdeadlines,follow-up,identifypotentialproblems,givefeedbacktootherworkpackages
20-21April2016 AGILEMEETING,BERLIN 19
![Page 20: 2016 07-20-wp8-q2 f2 f berlin](https://reader031.fdocuments.net/reader031/viewer/2022030304/587a9cbc1a28ab09758b6209/html5/thumbnails/20.jpg)
D8.1ToCIntroductionOverallApproachandMethodologyPilots(ContentfromGoogleDocuments)◦ Storyline◦ Users,rolesetc.◦ UseCases◦ …
IoTTestbedRequirementsAnalysisPilotArchitecturePilotOperation/Milestones/TimelineConclusion
20-21April2016 AGILEMEETING,BERLIN 20
![Page 21: 2016 07-20-wp8-q2 f2 f berlin](https://reader031.fdocuments.net/reader031/viewer/2022030304/587a9cbc1a28ab09758b6209/html5/thumbnails/21.jpg)
Thankyou!
20-21April2016 AGILEMEETING,BERLIN 21