case description
This test case aims at guiding the users to add an IOT device to the platform, add data to the platform, create a dashboard with added data and device together with those already present in the platform and associated with the city/organization, and finally to manage the access and privacy rules for managing the added data and produced dashboards and tools. The user is supposed to have an IOT Device (this device can be already registered to an IOT broker or not). The user would be guided in connecting the device to broker and platform, to collect the data coming from that device and show the data on a dashboard together with other data of the city or other data he has obtained from other users as well, or from its Mobile App.
|
|
|
|
|
|
|
|
e goal
Integrate and exploit personal data coming from personal IOT Devices together with data provided by the external services and by the city:
- Understand how to add IOT Devices to the platform
- Understand how to add different kinds of data to the platform
- Understand how to create a dashboard exploiting different kinds of data
- Understand how to manage the privacy of data types: IOT Device, data, MyKPI, dashboards, at least.
scenario
General information
|
Intended user group |
|
|
Link to the application |
|
|
Contractor help line |
Main contact point: snap4city@disit.org Contact form: https://www.snap4city.org/drupal/contact Direct Contacts:
|
|
Link to the documentation, video material ... |
HOW TO: add a device to the Platform https://www.snap4city.org/drupal/node/474 HOW TO: add data sources to the Platform https://www.snap4city.org/drupal/node/475 https://www.snap4city.org/drupal/node/473 HOW TO: define privacy rules for personal data, produced by the end-users own device |
|
Access rights |
The user can register on the Https://www.snap4city.org portal performing the registration on the Helsinki Organization. |
Pre-test conditions
The user has:
- a PC with browser: preferably Chrome or Firefox, with HD resolution screen
- been registered on the Snap4City.org portal
- been registered as Helsinki organization
- an IOT device which can be connected to an IOT Orion Broker
Post-test conditions
In order to complete the experience, the user has to:
- Perform the following step-by-step actions;
- Fill online survey
https://docs.google.com/forms/d/e/1FAIpQLSdAMN1NJL1q5aBjDjMtRFT71fF6nbjYlZX5ybdujDNwhKHW0g/viewform
Test-scenario (incl. step-by-step actions)
- Go on Snap4City portal: https://www.snap4city.org
- Login with your username and password
Understand how to add IOT Devices to the platform https://www.snap4city.org/drupal/node/474 for a more complete version
The IOT Device that you have it could be: (in green the most probable case for Antwerp)
- Already registered on an IOT Broker of your/city organization. In this case, who provided you the IOT Device may have provided also at least: an IOT Device Identifier, a description of the data produced by the Device, the protocol kind and the IOT Broker in which it is registered, etc. For example: device ID: es286481295, temperature and humidity, NGSI, the “orionFinland” IOT Broker on https://ngsi.fvh.fi or the “Antwerp” IOT Broker on https://ext-api-gw-p.antwerpen.be. In order to exploit the data of your IOT Device in the Platform, you
- have an IOT Device which is registered on an IOT Broker (for example, you received with the IOT Device the name of the IOT Broker) that is registered to Snap4City. You have two cases:
- the IOT Device has been **already registered** on Snap4City by the organization/city. This case can be verified by using the steps described in:
- See in this case: HOW TO: verify if an IOT device is registered and accessible for me.
- if the IOT device is registered please note that you are in case A3, if not, go at case A1.2
- the IOT Device is **not yet registered** on Snap4City (for example when a IOT Broker is managed by a third organization for security aspects, for example the FHV or DIGIPOLIS, or IMEC, ...), they given to your the device to test on different platforms.
- need to access IOT Device data without registering the IOT Device in the Snap4City platform and Broker, you need to know some configuration parameter of the IOT Broker and IOT Device, and Snap4City IOT App can get data directly from the IOT broker of your device without the need of having the Broker officially registered on snap4City.
- See in this case: HOW TO: add IOT Device data source from external broker to the platform.
- the IOT Device has been **already registered** on Snap4City by the organization/city. This case can be verified by using the steps described in:
- have an IOT Device which is already registered to an internal Snap4City IOT Broker (a IOT Broker managed by Snap4City for security aspects). In this case, the IOT Device and corresponding data are immediately accessible, and you can find them into the list of your data in the Data Inspector view, for Dashboards, etc., go in the Data Inspector to search your data by GPS location, name, nature as you like.
- have an IOT Device which is registered on an IOT Broker (for example, you received with the IOT Device the name of the IOT Broker) that is registered to Snap4City. You have two cases:
- Not registered to an IOT Broker. In this case, you need to know, at least, how the IOT Device works and how it can be internally configured to communicate with an IOT Broker: to authenticate, register, etc. So that you need to know: an IOT Device Identifier, a description of the data produced by the device, the protocol, etc. For example: device ID: 286481295, temperature and humidity, NGSI with basic authentication,
- In this case, the first step is to register the IOT Device to an IOT Broker. Snap4City offers you a number of Snap4City IOT Brokers compliant with different protocols to which you can connect your device. To this end, please follow this tutorial:
- in alternative you can find some other brokers in your area according to the protocol of your device.
- Once registered the IOT Device to an IOT Broker please restart from case (A); if you registered with a Snap4City IOT Broker it will be easy an (A2).
- In this case, the first step is to register the IOT Device to an IOT Broker. Snap4City offers you a number of Snap4City IOT Brokers compliant with different protocols to which you can connect your device. To this end, please follow this tutorial:
Understand how to add different kinds of data to the platform https://www.snap4city.org/drupal/node/475 for more complete version
Data can arrive to the platform by using different kinds of data sources, different protocols, formats, etc. In most of the IOT smart city platforms, many of the following cases are not addressed, and thus their approach could be at the first glance simpler, while in reality it is only strongly limited.
In Snap4City all cases are addressed and are from the simplest to the more advanced are:
- IOT Device data via some IOT Broker. (see HOW TO: add a device to the Platform). The IOT Device can be added to an:
- internal Snap4City IOT Broker (a broker managed by Snap4City for security aspects). In this case, the data are immediately accessible, and you can find them into the list of your data in the Data Inspector view, for Dashboards, etc., go in the Data Inspector to search your data by GPS location, name, nature as you like.
- external Broker (a broker managed by a third organization for security aspects). This means that the IOT Device has to be accessing only with specific authentication mechanisms. See
HOW TO: add IOT Device data source from external broker to the platform.
- Files on your local computer.
- please follow the step by step process included into
TC9.13: How to upload a local file into your IOT Application
- WebPages with data source inside.
- please follow the step by step process included into
TC9.16 Web Scraping to get data from web pages
- Open Data file on some Portal. The Open Data can be ingested into the Portal according to different mechanisms, they can be static (do not change) or dynamic (change with some rate, e.g., one every day, once per week). CKAN service of your city, you can set the Snap4City DataGate to access at that CKAN to get them automatically. See:
- please follow the step by step process included into
TC6.1. Managing Data Sets via DataGate: ingest, search, download, upload, annotate, share
- REST Call services API as MicroServices data sources. They can be treated as External Services (see above) or they can be registered on the platform to be queried directly from IOT Application as MicroService. In this case you need to register them:
- please follow the step by step process included into
TC2.25. Registering external MicroService calling RestCall services, using it on IOT applications
In all these cases, the data ingested are saved into your private storage as MyKPI data on which you can manage access and rights, use them for Dashboards, perform data analytic, etc.
- please follow the step by step process included into
HOW TO define privacy rules for personal data, produced by the end-users own device
Once the device and the data are added to the platform, they can be used to create dashboards together with other data sources already available on the platform:
- please follow the step by step process included into HOW TO: create a Dashboard
Understand how to create a dashboard exploiting different kinds of data
https://www.snap4city.org/drupal/node/473 for a complete manual
- Starting from one of the Dashboards list views (https://www.snap4city.org/dashboardSmartCity/management/dashboards.php ) in the Dashboard Manager, click on the orange button “New Dashboard” on the top-right
- Select one of models proposed for example “Selector and POI”
- Assign a name and then Click on Next
- The Dashboard Wizard is open and you can select Data vs graphics to be used for rendering them on dashboard widgets.
- After selected some data you can select among the possible graphic rendering of them.
- Then click on NEXT to create the dashboard
Understand how to manage the privacy of data types: IOT Device, data, MyKPI, dashboards, at least. https://www.snap4city.org/drupal/node/476 for a more complete version
By following the next instructions, you can manage the privacy of data types: IOT Device, data, MyKPI, mobile phone, dashboards. So that you manage
- an IOT Device that you have connected to the platform by following the steps described in HOW TO: add a device to the Platform The privacy rule can be applied to the IOT Device, and to single IOT Device data (also called sensors/actuators) as in:
- please follow the step by step process included into TC9.11. Management of Delegations on an IoT Device
- please follow the step by step process included into TC9.12. Management of Delegations on a sensor of an IoT Device
- a personal data as MyKPI, POI collected or internally produced in some how as described in
- please follow the step by step process included into HOW TO: define privacy rules on your MyKPI, POI, personal data
- a Mobile phone data (tracks and clicks) on which you have installed the new generation Mobile Apps such as "Helsinki in a Snap", or "Antwerp in a Snap", mobile Apps from Google Play Store or other stores, as described in HOW TO: Define privacy rules on Mobile Tracks and Click personal data collected from Mobile
- a Dashboard: please follow the step by step process included into
Links to other examples to manage personal data according to GDPR, please follow the next links to manage:
- to manage your user profile data (name, email, ): view, edit, delete
My Personal Statistics and Bounds: daily or Monthly
- to access at your statistics about the data access and volume of resources used and transactions performed over time (also with respect to the limits of the own accounts, that may depend on the Organization at which one belong and on the role in the profile): view (the delete are performed by other pages)
My Personal Data, My KPI and My POI
- to manage your personal MyKPI, MyPOI and trajectories, if any: view, edit, delete, delegation in access, revoke delegation, make public, change ownership
- to manage your personal engagements received on the Mobile Apps, auditing, if any: view, delete
- to manage your IOT Devices in which it is possible to: edit, delete, make public, delegate in access, revoke delegation, change ownership
- to manage your IOT Applications in which it is possible to: delete, restart, change ownership.
- to manage your Dashboards in which it is possible to: edit, delete, change ownership, delegate in access, revoke delegation, see list of delegations, make public.
Fill online survey
Filling the survey of this case.
https://docs.google.com/forms/d/e/1FAIpQLSdAMN1NJL1q5aBjDjMtRFT71fF6nbjYlZX5ybdujDNwhKHW0g/viewform