US1. Using City Dashboards

Snap4City provides two main modalities of creating dashboards, using:

  • Dashboard Builder of Snap4City
    • For accessing and browsing data on: Elastic Search, Mongo, MySQL, Smart City API, Super and thus from federated Smart City API, etc.
    • Supports sensors/actuators: data driven data, maps in extended manner, data driven widgets, large  collection of widgets, direct IoT Connections, custom widgets, animated PIN on maps, a large set of panel/widgets, etc.
    • Very simple to be used for control room, decision makers, situation rooms, operators, etc.
    • Very well integrated with IoT App, Custom widgets, animation, external services.
    • Very simple to be customized for non programmers since all the tools are visual.
    • Support for GDPR and deep control of access.
  • Kibana (so called DevDash, AMMA and recently My Dashboard (Dev) Kibana ), also accessible as Grafana
    • For accessing and browsing data on Elastic Search storage and other sources supported by Kibana/Grafana
    • No Support for real time event driven widgets/panels, actuators and synoptics, no sophisticated maps, etc.
    • Not simple for control room, decision makers, etc.
    • Not integrated with IoT App, Custom widgets, animation, external services.
    • Oriented to developers, complex production of custom views, etc.
    • Partial support of GDPR and deep control of access.

The following test cases are mainly forDashboards of Snap4City native in Dashboard builder 

 

Return to How to: User Scenarious and their List of Test Cases