Dashboard Management System

Dashboard Management System
Dashboard Management System
Dashboard Management System
This tool has been developed in the context
of REPLICATE H2020 project
V0.2.4
DISIT Lab
University of Florence
Department of Information Engineering
1
Dashboard Management System
Indice
Sommario
1.
Introduction ......................................................................................................................................................................4
2.
Dashboard System Manager Features...........................................................................................................................5
3.
Architecture of Dashboard System ...............................................................................................................................7
3.1.
4.
Deploy Notes ...............................................................................................................................................................9
Designing and editing Dashboard .............................................................................................................................. 10
4.1.
Create a new dashboard........................................................................................................................................... 11
5.
Designing and Editing Widgets .................................................................................................................................. 12
6.
Available Widgets details.............................................................................................................................................. 15
6.1.
Available widgets ...................................................................................................................................................... 15
6.2.
The Generic Widget properties .............................................................................................................................. 16
6.3.
The Widget Detailed information .......................................................................................................................... 17
7.
Details per widgets ........................................................................................................................................................ 17
7.1.
widgetBarContent ..................................................................................................................................................... 17
7.2.
widgetColunmContent............................................................................................................................................. 17
7.3.
widgetEvents ............................................................................................................................................................. 18
7.4.
widgetGaugeChart .................................................................................................................................................... 19
7.5.
widgetRadarSeries ..................................................................................................................................................... 20
7.6.
widgetGenericContent ............................................................................................................................................. 21
7.7.
widgetTimeTrendCompare ..................................................................................................................................... 22
1.1.
widgetPieChart .......................................................................................................................................................... 22
7.8.
widgetPrevMeteo ...................................................................................................................................................... 24
6.11
widgetSce ................................................................................................................................................................... 24
7.9.
widgetSingleContent ................................................................................................................................................ 25
7.10.
widgetSmartDS..................................................................................................................................................... 25
7.11.
widgetSpeedometer.............................................................................................................................................. 26
7.12.
widgetTimeTrend................................................................................................................................................. 26
7.13.
widgetTrendMentions ......................................................................................................................................... 26
7.14.
widgetStateRideAtaf ............................................................................................................................................ 27
7.15.
widgetServiceMap ................................................................................................................................................ 28
7.16.
widgetButton ........................................................................................................................................................ 28
7.17.
widgetProcess ....................................................................................................................................................... 28
7.18.
widgetProtezioneCivile ....................................................................................................................................... 29
7.19.
widgetExternalContent ....................................................................................................................................... 29
7.19.1.
Add a traffic flow map in a widget ExternalContent ..................................................................................... 29
2
Dashboard Management System
7.19.2.
Add a WiFi map in a widget ExternalContent ................................................................................................ 29
7.20.
widgetTable ........................................................................................................................................................... 30
7.21.
widgetLineSeries................................................................................................................................................... 31
7.22.
widgetCurvedLineSeries...................................................................................................................................... 31
7.23.
widgetBarSeries .................................................................................................................................................... 32
Annex I – Available metrics ................................................................................................................................................. 33
3
Dashboard Management System
1. Introduction
In the development of Smart City there is a great emphasis to the set-up of what is called Smart City Control
Room, SCCR. An SCCR is a substantially an area (of one of more rooms) in which all the high-level data are
summarized and made accessible for the decision makers and for the city operators.
In large metropolitan cities the SCCR include large panels/monitors (even covering large walls) in which the
status of the city is reported presenting the view of the city with some synthesis of data regarding: mobility,
energy, social, environment, weather, public transportation, people flow, health, water, security, ICT,
governmental, first aid, civil protection, police (118/112), and thus almost all the city resources. Most of the City
resources are in effect network of resources deployed in the city, and thus some of them are considered critical
infrastructures for the city functionality and life of city users such as: transportation, energy, security, health,
water, civil protection, etc.
Typically, in medium sized cities, the daily management of city resources is performed by a set of separate city
operators such as: energy operator, water providers, several telecom operators, several ICT infrastructures for
the different level of govern to provide different services, civil protection, etc. This means that all of these
separate city operators are autonomously managing their control room, with access at their own data to take their
own and limited decisions. For example, when the energy network has a problem in an area of the city the energy
is rerouted to reach the area via a different path, when the water network has a problem valves on tubes are
controlled and water is provided in other means, in presence of traffic congestion the red light timing is acted to
facilitate the flow and bus paths may be changed/rescheduled.
The presence of a set of independent control rooms may be positive to be reactive and solve microproblems. On
the other hand, in presence of relevant disasters the distributed solution is not efficient and effective as it should
do for the lack of concertation and synchronization of knowledge and actions. In addition, in some cases,
cascade effect may be provoked. For example, a water flooding may provoke lack of energy and communication,
the lack of garbage collection may provoke health problem, the lack of water quality may provoke health
problems, etc.
To cope with this kind of problems, in many countries, for the small and medium size cities an integrated control
room, a sort of situation emergency room is formally foreseeing and automatically created when critical
situations are detected.
In that case, representative people and devices, control panels, of each city operators are moved and activated in
a single place, even if for a temporary period. This approach reduces the communication time, and reduce the
misunderstanding among operators, while does not solve all the lack of synchronization among the city
operators, and the lack of integrated views for the city data. As put in evidence before, most of the critical events
in the city impact on multiple infrastructures, and may provoke cascade effects. Thus, the single city operator is
not in the condition to solve the problem, and in most cases, neither to identify the cause of the detected
problem. This problem can be solved by activating cross information among the several control rooms of the
city operators, and better to have a stable SCCR.
One identified and understood the need of having an integrated SCCR, immediately growth up the issue
regarding what has to be shown on (i) the panels on walls and what on (i) computers of the operators. These
approaches are very complex to be managed since the amount of information is very at wide range and has to be
easily understood by the observers of the panels on the wall and of the computers. It is not only a problem of
usability is a problem of understandability, a problem of data representation, a problem of competence for the
observers, the operators, the decision makers, etc.
In most cases, they have to be trained to understand the graphics representation. They have to become confident
on what they see to understand in deep all the single details represented on the screen. For example, all of us we
are used to understand: (i) a traffic representation observing the city map with red, orange, yellow, and green
4
Dashboard Management System
segments on the streets; (ii) a temperature and the humidity percentage, etc., while it is more difficult to read the
pollution, pollination, etc. Alarm signals in red, blinking signal, etc., may help on learning and on understanding.
From the technical point of view, the tools for rendering information on SCCR are typically called Dashboard.
The Dashboards should be capable to present real-time data in several different manners with real time updates
autonomously H24 7/7 days. Dashboard for control rooms should not be confused with business intelligence
tools that produce graphics from the combination of data extracted from some sources (database, files, API,
etc.).
The Dashboard Builder is a tool that allow to produce multiple dashboard accessing at static and real-time data
from some data store and services.
This manual is specific for users that are interested to design and edit dashboards on the basis of yet defined
metrics and widget. It is not a technical manual.
If you are interested in how to create a new metric, please note that a specific technical user manual is available
for this: Dashboard Builder User Manual: Management [http://www.disit.org/7074
If you are interested in how to design and add a new widget in the dashboard builder tool, please note that a
specific technical user manual is available for this: Dashboard Builder User Manual: Widget Model Designer [link]
If you are interested in how to install the Dashboard Builder tool, please note that a specific manual is available
for this: Dashboard Builder User Manual: Installation [http://www.disit.org/7074
2. Dashboard System Manager Features
The following is a list of features covered by the dashboard builder. In particular, the dashboard builder is able
to:
•
•
•
•
•
•
•
•
show graphics by using several different kinds of visual paradigms, and parameters;
showable on control room screens H24, 7 days per week;
enable the visualization to specific users even if they are not user of the control room. Visualize
dashboard to public or limited in access to a number of qualified users. This would allow to create
Dashboard for general public, and versions with sensitive data for the Civil Protection, police 118, etc.
render dashboards of different size from PC to mobile, with or without main header and frame. Please
note that responsiveness is not so relevant if a Dashboard is designed to stay H24/7 from UHD to small
mobile would be almost impossible to have the same user experience. If the aim is to provide with the
Dashboard as a monitoring tool, it has to be firstly efficient in that activity and secondly in the
interactivity and responsiveness;
show data taken from different Data Sources: SQL database, database via ODBC, noSQL database (for
example MongoDB, Hbase), HDFS directly or via Phoenix, RDF stores via SPARQL, from API calls
and from streaming data.
be composed as a set of Widgets of different size, allocated on a grid, by using a visual combination of
Widgets;
show data coming from some data lake, virtual store;
collect data and make replay of the data from a given date and time. This feature is adopted to play back
eventual critical condition and shown data
The dashboard builder allows also to:
•
•
•
•
control size and zoom of the Widget of the Dashboard;
set and change parameters as: size, color of the background, font of the header, color of the header, etc.
compose a set of possible views (in most cases called widgets), by visual interaction, visual composition
of widgets;
create and editing Dashboard produced by one or more users;
5
•
•
•
Dashboard Management System
edit controlling each single Dashboard by a single person;
allow each single dashboard to be viewed/accessed in reading by one or more specific people;
be cloned to derive a new dashboard from a former one and perform versioning;
Dashboard Widget is:
•
•
•
capable to show data according to different paradigms, graphics models (for showing and collecting
data)
o Classic graphic Widgets:
 tables (single and multiple columns and rows);
 graphs (single and multiple values), trend compare (hours, week, day, 12 hours, a month, an
year);
 pies diagrams, simple and multiple;
 kiviat: simple and multiple;
 direct values with unit of measure: a tile with the temperature, a tile with the number of
accesses in the last 10 minutes;
 histograms with multiple values/bars, vertical and horizontal, different colors;
 gauge: round bar with multiple colors and firing conditions;
 tachymeter: with multiple colors and firing conditions;
 images, photos, etc.;
o Map based Widgets:
 one or more elements on map with their: paths, areas, position, etc.
 position of public busses, position, lines, stops, status, forecast, etc.;
 parking status, position, status and predictions;
 panels for Variable Messages: position, status text;
 recharge stations, position and status of the recharge;
 process monitoring from the DISCES scheduler, Distributed Smart City Engine Scheduler
 Web site monitoring status verifying a textual pattern into a Web Page file;
 Wi-Fi status in real time, and clustering of trends;
 heat maps for the most requested/visited places;
 maps with controlled/added pin, POI (using OSM and/or Google Map or ServiceMap),
 traffic flow densities, Traffic flow reconstruction;
 real time position of busses and/or other vehicles;
o Special Widgets:
 List of Tweets, list of Hashtags on Tweets, List of Citations on Tweets;
 Weather forecast, pollution, pollination;
 Special list of events of different kinds: traffic, civil protection, health, etc.;
 First Aid data, status for several different hospitals on the territory, overview and real time
status details per hospital;
 TV camera for monitoring the city and security, according to different protocols:
 Smart DS, Italian flag, as metrics taken from some source or from SmartDS solution and
tools;
 Energy consumed, energy saved/stored, etc.;
 Civil protection status;
o External web pages as IFRAMES, third party
 web pages or third party tools;
o Be flexible being capable to change colors, fonts of the text, details of the graphics elements
(Actuator Widgets:
 buttons, sliders, commutators, text box, switch on/off, percentage of light (for collecting
data);
thickness of lines, etc.);
present a button (i) for getting information about the specific Widget;
6
•
•
•
•
•
•
•
•
•
•
•
Dashboard Management System
present a micro button (i) for each metric on tables for providing a popup on which the user can read
the description of the data listed/shown;
present the possibility of associating to each element of the Widget a call to an URL and thus to open
some web page;
be sensible at the mouse passage to show some evidence about the data shown, value, date, thresholds,
etc.;
be capable to refresh the data according to a periodic time by setting it per widget, coherently with the
refresh setting/value of the corresponding metric. For example, a temperature is read every X seconds,
while the corresponding Dashboard has been set up to request an update every 10 minutes;
be capable to provide the evidence of the periodic update of data and of the fact that the information is
changing. This requirement may be satisfied by providing period updated, thus reloading of the data and
may be showing some animation that are remarking when the data is updated;
be capable to be updated with different time interval with respect to the other widget of the same
Dashboard;
be capable to embed into third party web pages into the widget;
be open to host and thus to create new widgets by programming, for example in PHP, Java, Python, may
be using third party libraries on it for: TVcamera, graphics, execution, stream,..;
be capable to communicate with other widgets in the same Dashboard, for example from a widget
button at the push to activate a different graph in another Widget of the same dashboard;
be associated with one or more Data Sources to extract specific Metric;
allow to set-up of one or more reference firing rules on the data rendered and visualized by the widget.
The firing rule may provoke: (i) evidence in the graph as lines for thresholds, (ii) highlight and blinking
the widget when the firing condition become true and off when return false, (iii) send notification to
several different targets by using a range of mechanism such as: email, sms, API rest call; The
notification has to be sent by a Notificator service component.
The Metrics are specific selections/queries performed on some Data Source, and:
•
•
•
•
allow to take simple as well as complex data from some Data Source: SQL database, database via
ODBC, noSQL database (for example MongoDB, Hbase), HDFS directly or via Phoenix, RDF stores
via SPARQL, from API calls and from streaming data.
can be programmed to be refreshed, recollected with a given frequency.
Has to be collected autonomously even if the SCCR Dashboard in not shown in each time and day.
Collect data which can be saved or not on the Dashboard server and database. Data collected and saved
from metrics can be simple (float, integer, string, date/time, etc.) but also complex data in JSON or
other formats, ss well as data coming from some data lake, virtual store;
A Notificator is able to:
•
•
•
receive registration for new Widget, events, values trend;
log any kind of event sent, why, when to who, etc.;
pass the notification to a tool for managing tickets of intervention to an external tool;
3. Architecture of Dashboard System
In the following figure, the general architecture of the Dashboard solution is presented.
7
Dashboard Management System
According to the architecture the users can use the:
•
•
•
Data Mart for browsing and drilling down into Data Sources (SQL, noSQL, RDF, API etc.). To this end we
suggest using:
o Zeppelin for data base browsing for the following stores: ……………….,
o FLINT for SPARQL interface, for example on RDF stores;
o ServiceMap (http://servicemap.disit.org ) for knowledge base browsing over the city data as Km4City
knowledge base, which is RDF store as well;
o LOG (http://log.disit.org ) for browsing into any RDF store by using SPARQL and visual interface.
This tool allows you to browse all the RDF stores accessible in the world which provide a public end
point for SPARQL queries, from dbPedia, to Europeana, Geonames, Km4City, Camera, Senato,
Getty, etc.
Dashboard Management System (http://www.disit.org/dashboardSmartCity/management/ ) for:
o Setting up Data Sources: IP address, protocol, user name and password
o Setting up Metrics on the basis of accesses to Data Sources in terms of queries/call with the support
of DataMart tools.
o Load new Widget that can be created manually by using PHP. A Widget may render the same Metric
by means of different graphic models.
o Compose Dashboard exploiting Metrics and associating them to each Widget, composing widget
in the Dashboard frame. The Dashboards are created by using the visual interface of the Dashboard
Builder.
Notifier (……………………) to
o Set up firing condition/criteria for each Metric of each Widget instance in each defined Dashboard,
with the aim of computing criteria for sending notifications. For example, when Metric M is adopted
in Widget W of Dashboard D, the certain criteria is saved and controlled (M,W,D,C). One or more
criteria can be defined for each (M,W,D, C1….Cc), each of them may produce multiple Notifications,
N: (M,W,D, C1 (N1,…….., Nn),…., Cc(…)). The notifications can provoke emails, SMS, REST call,
as well as the activation of maintenance ticketing system.
o Log all the notification events.
In this view, there are two autonomous processes are active on the Dashboard solution:
8
•
•
Dashboard Management System
The Data Collector as Metric Engines, one or more processes dedicated to collect data from the several
Data Sources. The collected data can be (i) saved into a data base of Metric Historical Values, or can be (ii)
directly accessed from Widget/Dashboard for their visualization.
The Notificator, one or more processes that compute/verify the firing conditions (saved in their N.Settings)
and produce notifications. These notifications are also logged for further analysis and security evidence. The
notification process has to work even without any activation or view of Dashboard Instances. Moreover, the
Notificator has to provide the reference values of the firing conditions and the event of firing also the Widgets and Metrics since
they have to be visualized on the Dashboard as well.
As a conclusion, Dashboard Instances are available for view and activate corresponding widgets according to
their Settings. The saving of data into the database of Metric Historical Values, allows to keep track of what has
been visualized/monitored and thus enable the replay of data logged. On the other hand, it is also possible to
adopt widgets that (i) directly show/provide the data from in/out streams, respectively (for example, Civil
protection alert status, etc.); (ii) directly render/visualize web page segments into the Dashboard (for example for
showing social media analytics, traffic flow reconstruction tools).
3.1.
Deploy Notes
The Dashboard solution can be deployed on:
•
•
a single VM with all inside as well as on multiple VMs.
A very large solution is obtained by using:
• One or more VM the Data Collector as Metric Engines that could write on a common distributed
database for Metric Historical Values which can be an SQL like or HDFS with Phonenix
• One or more VM the Notificator that could write on a common distributed database for Metric
Historical Values which can be an SQL like or HDFS with Phonenix for logging events. Typically, a
classic SQL can be enough.
• One VM for the Dashboard Management System for creating new Dashboard, many users ion LDAP
can share the same solution.
• One or more VM with Dashboard Control Engine even in balance on the front end, which provide
access to the Dashboards.
A large range of intermediate solutions are viable as well according to your number of user accessing to the
Dashboards, and to the number of computed Metrics.
9
Dashboard Management System
4. Designing and editing Dashboard
To access to the tool it is necessary to inter Username and Password.
After this, the page will show the list of the whole dashboards that has been created and that are accessible for the
user.
The page shows in the right column the menu with the following items:
•
•
•
•
•
Dashboard Builder, that allows to create a new dashboard or to edit a yet available dashboard or to see a
preview.
Metrics: in this page, it is possible to create and modify metrics.
Widgets: in this page, it is possible to create or edit widgets. Please note that a specific section that explain
the available widgets is in this user manual;
Sources, to define or edit the data sources used by the metrics;
Users, to create new users to provide them the access to the tool.
10
4.1.
Dashboard Management System
Create a new dashboard
To create a new dashboard, click the “Dashboard Builder” menu item (1) on the right column and click the “Add
Dashboard” button (2) on the top of the page.
(1)
(2)
A new pop up will be shown that has to be used to define the structure and the basic layout of the dashboard, in
particular:
•
The name of the dashboard. The name
will be shown in the list of the available
dashboards (Menu: Dashboard Builder).
•
Title: the title of the dashboard that
will be shown on the top right of the
dashboard page
•
Subtitle (optional), that is shown
below the Title.
•
Header color
•
Header font size
•
Header font color
•
Background color
•
External frame color
•
Widget borders color
•
Dashboard color: an image in any
format and size. It will be resized automatically
and adapted to the available header space;
•
Dashboard logo link: to be opened if
the user clicks the logo;
•
Width: in terms of number of
columns, that is the unit of measures of the
dashboard. The number of columns is automatically converted in pixel width and percentage of width of
the monitor occupied and shown in the two corresponding fields below.
By clicking the “Create” button the dashboard will be saved and will be possible to populate it with widgets.
The following image show what each field of the form is representing. The widget inside is just an example.
11
Dashboard Management System
Title
Header
font size
Header
font color
Subtitle
Header
color
Dashboard
logo
Background
color
External
frame color
Widget borders
color
5. Designing and Editing Widgets
To add a new widget in a dashboard you have to enter in the edit mode. Click the edit button in the list of
available dashboards (Menu: Dashboard builder). A pop up will be shown asking to confirm that you want to
modify this dashboard.
Click “Modify” to confirm. You will enter in the dashboard edit mode.
As shown in the above image, a number of buttons will be shown on the top of the page (from left to right):
-
Add Widget, click here to add a widget in your dashboard;
Dashboard Properties, click here to modify the dashboard settings (see previous section);
Save Widgets Position, click here to save the current position of the widgets in the dashboard. In edit
mode, since you can move your widgets on the screen to find a better position, you should click here to
save the status when it is satisfactory for you;
Duplicate dashboard, click here to duplicate your dashboard. You will have to specify a new name for
your new duplicated dashboard;
Dashboard view, click here to see your dashboard in view mode. For a better experience we suggest to
visualize your dashboard by the browser in full screen mode;
Back to main menu, click here to exit to the edit mode without saving the current status. You will be
redirect to the page with the list of available dashboards.
To add a widget, click the Widget button with the plus (+). A new pop-up form will be open that will allow you
to select the widget you prefer and to set the corresponding parameters.
12
Dashboard Management System
(6)
(1)
(2)
(4)
(5)
(7)
(3)
As first step, you have to select the metric in the dropdown menu on top of the page (1). Once selected the
correct metric, click the Add button (2). You can add more different metrics and widgets to compose areas with
different widgets inside (if the number of added widgets exceed the page size, the widgets will be moved in the
next line).
In the Widget detailed information on the bottom right, it is possible to add a info description that will be shown
when the user clicks on the info button of the widget when published (3). According to the metric selected, you
will be able to select the Widget type (4). In the Widget type dropdown menu a list of widgets will be shown
coherent with the metric selected. If needed you can add a link to the widget that will be open if the user clicks
on the widget itself (5).
13
Dashboard Management System
The Generic widget properties on the top right are common for all widgets (6) whereas, once selected the widget, the
Specific widget properties will be shown on the bottom left of the page (7). These properties are different for the
various widgets. As example, the next image maps the fields available in the Generic widget properties form and
the widget areas (in this example the widget is a Speedometer).
In particular, in the Generic widget properties box it is possible to specify:
•
•
•
•
•
•
•
The title of the widget that will be shown in the header bar;
The color of the widget background;
The font size of the content text shown in the widget;
The font color of the content text;
The color of the header bar;
The color of the text of the header bar;
The period dropdown menu is available for specific widget types that represent values showed in a
period of time (also the last period can be compared with
a previous period of time by using the
TimeTrendCompare widget). The period shoed in the
widget can be 4 hours, 12 hours, Daily, Weekly, Monthly,
annually. These values have to be stored and available to
be showed correctly;
• Refresh rate represent the period of time the value in
the widget has to be refreshed. As default, every 60
seconds the widget is refreshed but this refresh rate value
has to be set according to the metric since it is not useful
to update and refresh every 60 secs a widget representing
a value updated for example 1 time per day;
• Height and width are expressed in columns;
• The unit of measure of the value to be shown in the
widget.
14
Dashboard Management System
6. Available Widgets details
The widget is a graphical elaboration of data ( Php File). It is usefull to represent some Metrics in a different and
graphic user-friendly way.
6.1.
Available widgets
The following tables shows the list of all the widgets available with information about minimun/maximum
number of column and rows and the type of graphical representation.
Widget name
min columns max columns
min rows
max rows
Type
widgetBarContent
2
50
2
50
Percentage
widgetColunmContent
2
50
2
50
Percentage
widgetEvents
2
50
2
50
Textual
widgetGaugeChart
2
50
2
50
Percentage,
Integer
widgetRadarSeries
2
50
2
50
Series (table
of values)
widgetFirstAid
2
50
2
50
Textual
widgetGenericContent
2
50
2
50
Percentage,
Integer,
Textual
widgetTimeTrendCompare
2
50
2
50
Percentage,
Integer, Float
widgetPieChart
2
50
2
50
Percentage or
Series
widgetPrevMeteo
2
50
2
50
Textual
widgetSce
2
50
2
50
SCE
widgetSingleContent
2
50
2
50
Percentage,
Integer, Float
widgetSmartDS
2
50
2
50
Percentage
widgetSpeedometer
2
50
2
50
Percentage,
Integer, Float
widgetTimeTrend
2
50
2
50
Percentage,
Integer, Float
widgetTrendMentions
2
50
2
50
Textual
widgetStateRideAtaf
2
50
2
50
Percentage
widgetServiceMap
2
50
2
50
Map
widgetButton
1
50
1
50
Button
widgetProcess
2
50
2
50
Textual
widgetProtezioneCivile
2
50
2
50
Textual
widgetExternalContent
2
50
2
50
Textual (URL)
widgetTable
2
50
2
50
Series
widgetLineSeries
2
50
2
50
Series
widgetCurvedLineSeries
2
50
2
50
Series
15
Dashboard Management System
Widget name
min columns max columns
min rows
max rows
Type
widgetBarSeries
2
50
2
50
Series
widgetTrafficEvents
2
50
4
50
Textual
widgetResources
2
50
4
50
Textual
widgetNetworkAnalysis
2
50
4
50
Textual
Some of the above listed widgets are specific for only one metric and cannot be used for others (this means that
a metric can be represented in the dashboard by using only one specific widget). For example:
•
•
•
•
•
•
•
•
•
•
widgetFirstAid can be selected only for the metric FirstAid;
widgetEvents can be selected only for the metric List_Events_FI_Day;
widgetPrevMeteo can be selected only for the metric Previ_Meteo;
widgetTrendMentions can be selected only for the metric MentionsTrends_FI_Day;
widgetProcess can be selected only for the metric Process;
widgetProtezioneCivile can be selected only for the metric ProtezioneCivile;
widgetExternalContent can be selected only for the metric ExternalContent.
widgetTrafficEvents can be selected only for the metric TrafficEvents
widgetResources can be selected only for the metric Resources
widgetNetworkAnalysis can be selected only for the metric NetworkAnalysis
6.2.
The Generic Widget properties
Title: title of the widget
Background color: background color of the widget
Content font size: font size of the values showed in
the widget
Content font color: color of the font in the widget
Header color: color of the header bar
Header text color: color of the text in the header
bar
Period: this field is available for values that are
historicized and that can be represented as a trend
for a period of time. Period can be 4 hours, 12
hours, Daily, Weekly, Monthly and Annually. This
field is available only for the widgets
TimeTrendCompare and TimeTrend.
Refresh rate of the widget: time expressed in
seconds
Height and Width of the widget expressed in
number of columns
Unite of Measure (U/M): in this field it is possible
to specify the unit of measure of the value shown
in the widget. For some metric, this field could be
not available
Unite of Measure (U/M) position: in this field, it is
possible to specify the position of the unit of
measure text. With respect the position of the
value in the widget, the unit of measure can be
positioned next to it or below it. For some metric,
this field could be not available
16
6.3.
Dashboard Management System
The Widget Detailed information
For each widget it is possible to define and visualize some information that are shown as a popup if the user
click the info button
in the top left corner of the widget in view mode. This information can be written
by using the text editor available in the Widget detailed information box below the Generic widget properties.
7. Details per widgets
In this section, the look and feel of each widget with the associated specific parameters and properties are
explained.
Every widget can represent values (typically integer numbers, float numbers, percentage, text content, series of
data from a table) and can have its Specific Widget Properties.
7.1. widgetBarContent
The widget BarContent shows an horizontal green bar representing a percentage. Generic properties are
explained in section 6.2.
Please note that the following generic properties are not available for this widget: period, unit of measure, unit of
measure position.
The green bar shows the percentage of the
selected metric. The complementary value is
automatically calculated.
For this widget, there are not Specific Widget Properties available.
7.2. widgetColunmContent
The widget ColumnContent shows a vertical green bar representing a percentage.
The green bar shows the percentage of the
selected metric. The complementary value
is automatically calculated.
17
Dashboard Management System
For this widget there are not Specific Widget Properties available. Generic properties are explained in section 6.2.
Please note that the following generic properties are not available for this widget: period, unit of measure, unit of
measure position.
7.3. widgetEvents
The Events widget is specific for the metric List_Events_FI_Day and shows the list of public events available in
Florence in the day.
The list is divided in two columns: in the first column on the
left, for every event, there are two icons specifying the type of
the event and if the event is free or not. The icons specifying the
type of the event are categorized for the following typologies of
events:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Title
When?
Where?
Show on map
(via cross widget)
Other event
Special openings
Estate Fiorentina
Local fairs, markets
Film festival
Exhibition
Classic music, opera and ballet
Rock music, jazz, pop, contemporary
News
Readings, conferencies, congress
Readings, book club thing
Sport
Theater
Popular tradition
Walking
Below the type of event icon, the second one provides
information about the event’s cost:
•
•
Paid event
Free event
Form each event, the following information are shown: the
event title, the duration (from, to) and the location. Colors are
automatically set by the system.
18
Dashboard Management System
For this widget, there are Specific Widget Properties settings
available that allows to specify the widget where to show the
location of a clicked event (via a cross widget functionality) in a
map. The image on the left clarifies the specific properties
available for the Events widget.
The “Available geolocation widgted” drop-down menu, lists the
titles of the available widgets the can potentially show the
position of the event in a map. Substantially, the drop-down
menu shows the list of titles of ExternalContent widgets available
in the dashboard. The user has to select the widget that will show
the position of the event. The interaction is activated when the
user clicks on the “ON MAP” text after the address of the event.
In the Event show on the selected map drop down menu it is possible
to select the typology of event to be shown in the selected
widget. Multiple selections are admitted. This means that
different types of events, can be shown in different and
independent widgets and maps.
7.4. widgetGaugeChart
The widget GaugeChart shows a semicircle representing a percentage or an integer value. In case of an integer
value, the semicircle is entirely colored.
Percentage value
Integer value
Threshold
The yellow arc in the widget represents a threshold value that can be useful to set up notifications in case of
unexpected values. Please note that actually this threshold has to be manually set in the metric definition. Refer
to the manual on how to define metrics for more information.
Refer to section related to the notification tool for more information about the notification settings.
For this widget there are not Specific Widget Properties available.
19
7.5. widgetRadarSeries
Dashboard Management System
The RadarSeries widget allows to compare series of data in a radar chart representation. The following image
shows an example of RadarSeries widget clarifying how the chart has to be interpreted.
The names in the angles of the geometric
figure represent an observed quantity.
Every line (from the centre to the the angle)
represents an axis but note : the centre is the
origin (smaller values are closer to the centre).
You can also see the observed values.
In some cases you can see one or more dashed
lines. The dashed lines represent the thresolds
and you can add them in the Specific Widget
Properties.
The legend associates a different color to a
different context in which the quantities are
observed.
In the Specific Widget Properties box, you can change the X-Axis labels properties: font size (1) and color (2).
The X-Axis labels are the labels in the angles of the geometric figure representing an observed quantity (e.g.
CO2).
The Y-Axis labels are the labels of some reference values in the figure (eg. 0, 100, 200, etc.) and you can change
the font size (3) and color (4). The Data are the observed values quantity and it is possible to change the font
size (5) and color (6).
It is possible to change the Legend font size (7) and its color (8).
The grid helps to give you some reference points; you can choose its lines width (9) and its lines color (10) and
the lines width (11) and colors (12) of the lines referred to the values.
(1)
(2)
(3)
(4)
(5)
(7)
(9)
(11
)
20
(6)
(8)
(10)
(12)
Dashboard Management System
The colors of the lines representing metric values in the radar
chart, can be set automatically or manually, as shown in the
following image. By selecting the manual color setting, the box will
show values names represented in the selected metrics with the
possibility to define one specific color for each of them.
An important feature of this widget is the possibility to define thresholds that will be shown as dashed lines in
the radar chart. To set threshold values Switch the Set thresholds drop down menu from No to Yes (1), then:
(1)
(3)
(7)
• Set the Thresholds lines width (2).
(2)
• Press the button
(3).
• Choose the color of the dashed line (4).
• Write a short description (You can leave default value Empty)
(5).
• Choose the limit for every quantity in the table (You can leave
(4)
(5)
(6)
•
default 0) (6).
Remember to press Modify to save the new widget properties.
•
To remove the thresholds, press the button
(7).
7.6. widgetGenericContent
By using this widget it is possible to show up to three values from different metrics.
It’s composed of two parts:
•
Metric’s name (left side).
•
Metric’s observed value (right side).
(1)
(3)
(2)
To use this widget, you have to follow the following steps:
1.
Click the button to add a new widget in the dashboard;
2.
In the metric field, select on numeric metric (1) and
press Add (2);
3.
In the Widget type drop down menu select
widgetGenericContent (3);
4.
Select another metric in the metric drop down menu
and press Add;
5.
You can have up to three different metrics represented
in this widget.
6.
Set the Generic widget properties as you prefer;
For this widget there are not Specific Widget Properties.
21
7.7. widgetTimeTrendCompare
Dashboard Management System
This widget is useful to show the historical values evolution of a metric during a period of time in comparison
with a previous period (in the same time slot). The historical values of the previous period are represented with a
light grey line.
•
Current trend
•
Previous trend
•
Trend thresholds
•
Legend (show the current trend’s color and the
previous trend’s color).
Please note that the trend threshold has to be set manually
during the definition of the metric.
In the Generic properties it is possible to set the period of time
to be show in the widget (4 hours, 12 hours, daily, weekly,
monthly, annually) as shown in the image on the left.
For this widget there are not Specific Widget Properties.
1.1. widgetPieChart
This widget can have different representations, according to the type and the number of observed data available
in the selected metric to be represented.
In the case of a single value, this as to be a percentage and the Pie
Chart will show the value and will automatically calculate the
complementary value.
The Pie Chart widget can represent three or more values (a
series)3. The legend associates a different color to a different
observed value.
22
Dashboard Management System
The Pie Chart widget can also represent more complex data. The
image on the left show an example of the complexity that can be
represented. In this case the environmental values of different city
districts are represented (e.g. the observed values of pollution for
different quarters in the city).
The internal circular sectors represent the quarters while the
external circular sectors represent the pollution values for each of
them. In fact the two radius bordering a quarter, are also bordering
the observed values of the pollution substances in the quarter.
This widget has Specific Widget Properties that allow to define specific properties.
•
•
Legend font size and Legend font color: You can change legend font size and color.
Data labels distance, Data labels font size and Data labels font color: You can change the data
labels distance from the Pie Chart, font size and text color.
Inner radius: allow to define the radius of an empty circle inside
the Pie Chart. In the image on the left an Inner radius of 40 has
been defined.
90° start angle
Start angle (°) and End angle (°): allow to modify You can
modify these two options to obtain a different circular sector. In
the image on the left a Start angle of 90° and an End angle of 270°
has been defined starting from the same widget represented above.
270° end angle
23
Dashboard Management System
Diagram center Y(%):You can modify the Pie Chart vertical
position. Default value is 50. Higher values move the pie chart up,
smaller values move the pie chart down. In the image on the left a
value of 80 has been defined as exceeding example.
Slice colors: allow to
manually define the colors of
the slices in the pie chart. Press
the colored buttons to modify
the single colors.
Set Thresholds:
1. Switch Set thresholds from
No to Yes.
2. Press the button .
3. Choose the color.
4. Write a short description
(You can leave default
Empty).
5. Choose the limit for every
quantity in the table. (You
can leave default 0).
6. Remember to press Modify
button to save the new
widget properties.
7. To remove a threshold,
press the button
.
7.8. widgetPrevMeteo
This widget shows the weather of the current day and the forecast for the next four days:
•
•
•
image
a short description
a temperature range (min/max).
For this widget there are not yet Specific Widget Properties.
The weather forecast service is provided by the LAMMA consortium of the Tuscany Region
(http://www.lamma.rete.toscana.it).
6.11 widgetSce
This widget shows information related to the Km4City data center.
24
Dashboard Management System
•
CPU (1): The percentage of CPU
utilization.
•
RAM (2): The amount of RAM utlization,
expressed in GigaByte.
•
DAILY JOBS (3): The number of daily
executed jobs.
For this widget there are not yet Specific Widget Properties.
7.9. widgetSingleContent
This widget shows a single observed value. The Generic widget properties allow to define some settings like the
background color, the font size and color, the refresh rate, the width and the hight and the Unit of Measure
(U/M) that can be shown next to the value or below it.
Same widget with the Unit of measure position below the value
For this widget there are not Specific Widget Properties.
7.10.
widgetSmartDS
This is a widget is specific for the SmartDS_Process metric and is showing an example of a decision process
generated by the Smart Decision Support tool (http://smartds.disit.org/dss/). Click the following link for
additional information regarding SmartDS tool: www.disit.org/6711.
25
7.11.
widgetSpeedometer
Dashboard Management System
This widget shows a Metric value (Percentage, Integer,
Float) represented in a speedometer.
Via manual editing of the php code it is possible to set
color variations to highlight critical threshold.
For this widget there are not yet Specific Widget Properties.
7.12.
widgetTimeTrend
This widget is useful to show the historical values
evolution of a metric during a period of time.
In the Generic properties it is possible to set the
period of time to be show in the widget (4 hours,
12 hours, daily, weekly, monthly, annually).
As shown in the image on the left, it is possible to
specify different background color and font sizes.
For this widget there are not Specific Widget Properties.
7.13.
widgetTrendMentions
This widget shows the Twitter trend of a particular Twitter Vigilance channel (http://www.disit.org/rttv/).
Actually, this widget is set for a specific channel of the Twitter vigilance tool referred to Florence. For additional
information regarding the Twitter Vigilance tool, you can visit the following link: www.disit.org/drupal/6793
26
Dashboard Management System
This widget shows two tabs named Trends (the most used hashtag in the monitored Twitter Vigilance channel)
and Quotes (the most cited users in the monitored Twitter Vigilance channel).
In the Specific Widget Properties it is possible to set if the widget has to show by default the Trends tab, the
Quotes tab or automatically slide the two tabs.
7.14.
widgetStateRideAtaf
This widget shows the bus state lines through a tab having three different configurations :
• Bus lines State: This tab configuration shows the
percentage of bus in time, early bus and late bus.
• Monitored Lines: This tab configuration shows the
observed bus lines.
• Data: This tab configuration shows the time of the
last update.
In the Specific Widget Properties, it is possible to modify the Default tab’s configuration through the drop down menu
by selecting the different options available: Bus state, Lines, Data, None.
27
7.15.
widgetServiceMap
7.16.
widgetButton
7.17.
widgetProcess
Dashboard Management System
28
Dashboard Management System
7.18.
widgetProtezioneCivile
7.19.
widgetExternalContent
7.19.1.
Add a traffic flow map in a widget ExternalContent
http://www.disit.org/siimobilitytrafficflow2/?map=streets&position=43.7722,11.2541&zoom=15
map can be: streets, satellite or grayscale
zoom no more than 18
7.19.2.
Add a WiFi map in a widget ExternalContent
Ecco i parametri che si possono passare alle mappe con i valori possibili:
http://wifimap.km4city.org/wifi-firenze/ap/ap-clusters.php?title=Firenze+WiFi%3A+Access+Points+Clusters+Coverage+Map%26nbsp%3B
•
•
•
•
•
•
•
•
•
•
•
radius=[valore]
maxOpacity=[valore]
scaleRadius=[true,false]
useLocalExtrema=[true,false]
APs=[true,false]
APsSaturday=[true,false]
APsSunday=[true,false]
heatmap=[true,false]
legend=hidden
zoom: from 1 (entire world) to 22
position=long,lat as
http://wifimap.km4city.org/wifi-firenze/ap/streaming-realtime/streaming-realtime.php?title=Firenze+WiFi%3A+APs+Streaming+Realtime%26nbsp%3B
•
radius=[valore]
29
•
•
•
•
•
•
•
•
•
•
•
Dashboard Management System
maxOpacity=[valore]
heatmap=[true,false]
streamingAPs=[true,false]
timeRange=[5,10,15,30,60,180,360,540,720,1440,4320,10080,44640]
distinctPeople=[true,false]
localExtrema=[true,false]
clusteredMarkers=[true,false]
replySpeed=[0,10,30,60,300,900,1800,3600,7200]
legend=hidden
zoom: from 1 (entire world) to 22
position=long,lat
7.20.
widgetTable
30
Dashboard Management System
7.21.
widgetLineSeries
7.22.
widgetCurvedLineSeries
31
7.23.
widgetBarSeries
Dashboard Management System
32
Dashboard Management System
Annex I – Available metrics
In the following table, metrics yes available in the system are listed and described.
Name
Description
Area
Source
Widget type
Ataf_Rt
Percentage of real time
signals provided by ATAF
Mobility
Osservatorio
Regionale per la
Mobilità ed i
Trasporti
•
•
•
•
•
•
•
•
•
Bar Content
Column content
Gauge chart
Generic content
Time trend compare
Pie chart
Single content
Speedometer
Time trend
BikeSharing
Fake metric simulating bike Fake area
sharing data
Disit
•
•
•
•
•
•
Radar series
Pie chart
Table
Line series
Curved line series
Bar series
Bus_Active_Rt
Number of active busses
tracked in real time
Mobility
Osservatorio
Regionale per la
Mobilità ed i
Trasporti
•
•
•
•
•
•
•
•
Bar Content
Column content
Gauge chart
Generic content
Time trend compare
Single content
Speedometer
Time trend
Bus_Active_TT
Active busses on the basis
of the ATAF timetable
Mobility
Osservatorio
Regionale per la
Mobilità ed i
Trasporti
•
•
•
•
•
•
•
•
Bar Content
Column content
Gauge chart
Generic content
Time trend compare
Single content
Speedometer
Time trend
Bus_Position_Map
Real time position of ATAF Mobility
busses
Osservatorio
Regionale per la
Mobilità ed i
Trasporti
•
Service Map
Bus_State_Lines
Percentage of
delays/advance on the
available bus lines
Mobility
Osservatorio
Regionale per la
Mobilità ed i
Trasporti
•
•
Pie chart
State ride ATAF
null
null
•
Button
Fake area
Disit
•
•
•
•
•
Radar series
Pie chart
Table
Line series
Curved line series
Button
CarSharing
Fake metric simulating car
sharing data
33
Dashboard Management System
Name
Description
Area
Source
Widget type
•
Bar series
Car_Flow
Number of
Mobility
inbound/outbound cars per
day (interpolation and sum
based on sensors)
Osservatorio
Regionale per la
Mobilità ed i
Trasporti
•
•
•
•
•
•
•
•
Bar Content
Column content
Gauge chart
Generic content
Time trend compare
Single content
Speedometer
Time trend
CitiziensSatisfacion
Fake metric simulating
citiziens statisfaction index
Fake area
Disit
•
•
•
•
•
•
Radar series
Pie chart
Table
Line series
Curved line series
Bar series
CreatedEngagement
Km4City Created
Engagements
Statistics
Disit
•
•
•
•
•
•
•
•
Bar Content
Column content
Gauge chart
Generic content
Time trend compare
Single content
Speedometer
Time trend
DCHum1
DataCenter Humidity 1
Datacenter
Disit
•
•
•
•
•
•
•
•
Bar Content
Column content
Gauge chart
Generic content
Time trend compare
Single content
Speedometer
Time trend
DCHum2
DataCenter Humidity 2
Datacenter
Disit
•
•
•
•
•
•
•
•
Bar Content
Column content
Gauge chart
Generic content
Time trend compare
Single content
Speedometer
Time trend
DCTemp1
DataCenter Temperature 1
Datacenter
Disit
•
•
•
•
•
•
•
•
Bar Content
Column content
Gauge chart
Generic content
Time trend compare
Single content
Speedometer
Time trend
34
Dashboard Management System
Name
Description
Area
Source
Widget type
DCTemp1float
DataCenter Temperature 1
Datacenter
Disit
•
•
•
•
•
•
•
•
Bar Content
Column content
Gauge chart
Generic content
Time trend compare
Single content
Speedometer
Time trend
DCTemp2
DataCenter Temperature 2
Datacenter
Disit
•
•
•
•
•
•
•
•
Bar Content
Column content
Gauge chart
Generic content
Time trend compare
Single content
Speedometer
Time trend
Delay_IngestionAvm
AVM ingestion delay
Mobility
Disit
•
•
•
•
•
•
•
•
Bar Content
Column content
Gauge chart
Generic content
Time trend compare
Single content
Speedometer
Time trend
Delay_IngestionAvm_Line17
Ingestion delay line 17
Mobility
Disit
•
•
•
•
•
•
•
•
Bar Content
Column content
Gauge chart
Generic content
Time trend compare
Single content
Speedometer
Time trend
Delay_IngestionAvm_Line31
Ingestion delay line 31
Mobility
DIsit
•
•
•
•
•
•
•
•
Bar Content
Column content
Gauge chart
Generic content
Time trend compare
Single content
Speedometer
Time trend
Delay_IngestionAvm_Line6
Ingestion delay line
Mobility
Disit
•
•
•
•
•
•
•
•
Bar Content
Column content
Gauge chart
Generic content
Time trend compare
Single content
Speedometer
Time trend
35
Dashboard Management System
Name
Description
Area
Source
Widget type
EngagementCreated
Km4City Engagements
Created
Statistics
Disit
•
•
•
•
•
•
•
•
Bar Content
Column content
Gauge chart
Generic content
Time trend compare
Single content
Speedometer
Time trend
EngagementSent
Km4City Engagements Sent Statistics
Disit
•
•
•
•
•
•
•
•
Bar Content
Column content
Gauge chart
Generic content
Time trend compare
Single content
Speedometer
Time trend
EngagementUserEval
Km4City Engagements User Statistics
Eval Events
Disit
•
•
•
•
•
•
•
•
Bar Content
Column content
Gauge chart
Generic content
Time trend compare
Single content
Speedometer
Time trend
EngagementViewed
Km4City Engagements
Viewed
Statistics
Disit
•
•
•
•
•
•
•
•
Bar Content
Column content
Gauge chart
Generic content
Time trend compare
Single content
Speedometer
Time trend
EventsOverview
Fake metric simulating an
overview over city events
Fake area
Disit
•
•
•
•
•
•
Radar series
Pie chart
Table
Line series
Curved line series
Bar series
Events_FI_Day
Number of events in
Florence per day
Entertainment Comune di
Firenze
•
•
•
•
•
•
•
•
Bar Content
Column content
Gauge chart
Generic content
Time trend compare
Single content
Speedometer
Time trend
36
Dashboard Management System
Name
Description
ExternalContent
Area
Source
Widget type
It allows to visualize content External
coming from external
content
websites and webtools
Disit
•
External content
FirstAid
Florence main first aids
status
Disit
•
WidgetFirstAid with 3
different visualization mode:
single hospital totals mode;
single hospital details mode;
multiple hospitals overview
mode.
FoodPreferences
Fake metric simulating food Fake area
preferences
Disit
•
•
•
•
•
•
Radar series
Pie chart
Table
Line series
Curved line series
Bar series
Healthcare
Fake metric simulating
healthcare data
Fake area
Disit
•
•
•
•
•
•
Radar series
Pie chart
Table
Line series
Curved line series
Bar series
InternetConnections
Fake metric simulating
internet connections data
Fake area
Disit
•
•
•
•
•
•
Radar series
Pie chart
Table
Line series
Curved line series
Bar series
Km4City_Query_Day
Number of queries per day Statistics
on Km4city API (mobile or
web)
Disit
•
•
•
•
•
•
•
•
Bar Content
Column content
Gauge chart
Generic content
Time trend compare
Single content
Speedometer
Time trend
List_Events_FI_Day
List of the events of the day Entertainment Comune di
in florence qith various
Firenze
information
•
•
Events
MentionsTrends_FI_Day
Main trends/citations on the Social network Disit - Twitter
Twitter Vigilance Florence
Vigilance
channel per day
•
Trend mentions
Meteo_Rt
Percentage of working
weather measures
•
•
•
•
•
•
•
Bar Content
Column content
Gauge chart
Generic content
Time trend compare
Pie chart
Single content
Statistics
Meteo
37
Consorzio
LaMMA
Dashboard Management System
Name
Description
Area
Source
Widget type
•
•
•
•
SmartDS
Speedometer
Time trend
State ride ATAF
N_Active_Operators
Number of active operators Statistics
Disit
•
•
•
•
•
•
•
•
Bar content
Column content
Gauge chart
Generic content
Time trend compare
Single content
Speedometer
Time trend
N_Active_Tourists
Number of active tourists
Statistics
Disit
•
•
•
•
•
•
•
•
Bar content
Column content
Gauge chart
Generic content
Time trend compare
Single content
Speedometer
Time trend
N_Active_Users
Number of active users
Statistics
Disit
•
•
•
•
•
•
•
•
Bar content
Column content
Gauge chart
Generic content
Time trend compare
Single content
Speedometer
Time trend
N_triples
Number of M triple in the
RDF store
Statistics
Disit
•
•
•
•
•
•
•
•
Bar content
Column content
Gauge chart
Generic content
Time trend compare
Single content
Speedometer
Time trend
OD_Available
Number of available Open
Data
Statistics
Disit
•
•
•
•
•
•
•
•
Bar content
Column content
Gauge chart
Generic content
Time trend compare
Single content
Speedometer
Time trend
Park_Free
Percentage of free parking
areas
Mobility
Osservatorio
Regionale per la
Mobilità ed i
Trasporti
•
•
•
•
•
Bar content
Column content
Gauge chart
Generic content
Time trend compare
38
Dashboard Management System
Name
Description
Area
Source
Widget type
•
•
•
•
Pie chart
Single content
Speedometer
Time trend
Park_Free_FortezzaFiera
Percentage of free areas in
the Fortezza Fiera Parking
Parcheggi
Disit
•
•
•
•
•
•
•
•
•
Bar Content
Column content
Gauge chart
Generic content
Time trend compare
Pie chart
Single content
Speedometer
Time trend
Park_Free_MercatoCentrale
Percentage of free areas in
the Mercato Centrale
Parking
Parcheggi
Disit
•
•
•
•
•
•
•
•
•
Bar Content
Column content
Gauge chart
Generic content
Time trend compare
Pie chart
Single content
Speedometer
Time trend
Park_Free_Parterre
Percentage of free areas in
the Parterre Parking
Parcheggi
Disit
•
•
•
•
•
•
•
•
•
Bar Content
Column content
Gauge chart
Generic content
Time trend compare
Pie chart
Single content
Speedometer
Time trend
Park_Free_StazioneSMN
Percentage of free areas in
the Santa Maria Novella
Parking
Parcheggi
Disit
•
•
•
•
•
•
•
•
•
Bar Content
Column content
Gauge chart
Generic content
Time trend compare
Pie chart
Single content
Speedometer
Time trend
Park_Rt
Percentage of working
parking
Mobility
Osservatorio
Regionale per la
Mobilità ed i
Trasporti
•
•
•
•
•
•
•
•
•
•
Bar Content
Column content
Gauge chart
Generic content
Time trend compare
Pie chart
Single content
SmartDS
Speedometer
Time trend
39
Dashboard Management System
Name
Description
Area
Source
Widget type
•
State ride ATAF
Pollution
Fake metric simulating air
pollution
Fake area
Disit
•
•
•
•
•
•
Radar series
Pie chart
Table
Line series
Curved line series
Bar series
Pollution2
Pollution2
Fake area
Disit
•
•
•
•
•
•
Radar series
Pie chart
Table
Line series
Curved line series
Bar series
Previ_Meteo
Meteo measures in a
municipality
Meteo
Consorzio
LaMMA
•
Prev meteo
Process
Process status
Process status Disit
•
Process
ProtezioneCivile
Data provided by the Civil
Protection
API
Disit
•
Protezione civile
Q1
Energy consumption in the Energia
district Q1
Comune di
Firenze
•
•
•
•
•
•
•
•
Bar content
Column content
Gauge chart
Generic content
Time trend compare
Single content
Speedometer
Time trend
QAria_FI_GRAMSCI_NO2
Concentration of NO2 @
FI-GRAMSCI
ARPAT
•
•
•
•
•
•
•
•
Bar content
Column content
Gauge chart
Generic content
Time trend compare
Single content
Speedometer
Time trend
Recharge_Columns_Position_Map Position of the recharge
Mobility
stations for electric vehicles
Osservatorio
Regionale per la
Mobilità ed i
Trasporti
•
Service Map
Rivers
Disit
•
•
•
•
•
•
Radar series
Pie chart
Table
Line series
Curved line series
Bar series
Fake metric simulating
rivers data
Air Quality
Fake area
40
Dashboard Management System
Name
Description
Area
Source
Widget type
Sce_CPU
CPU percentage of use on
the SCE in absolute (data
from SCE)
Statistics
Disit
•
Sce
Sce_Job_Day
Number of processes
launched on the SCE per
day
Statistics
Disit
•
Sce
Sce_Mem
Memory used by the SCE in Statistics
absolute (data from SCE)
Disit
•
Sce
Sensors_Rt
Percentage of working
sensor flow
Mobility
Osservatorio
Regionale per la
Mobilità ed i
Trasporti
•
•
•
•
•
•
•
•
•
•
•
Bar Content
Column content
Gauge chart
Generic content
Time trend compare
Pie chart
Single content
SmartDS
Speedometer
Time trend
State ride ATAF
ServiceMap_Query_Day
Number of queries to the
ServiceMap tool per day
Statistics
Disit
•
•
•
•
•
•
•
•
Bar Content
Column content
Gauge chart
Generic content
Time trend compare
Single content
Speedometer
Time trend
Services_Access
Number of access to
services per day (web e
mobile)
Statistics
Disit
•
•
•
•
•
•
•
Column content
Gauge chart
Generic content
Time trend compare
Single content
Speedometer
Time trend
Services_Duplicate
Percentage of service
duplicated (name, address,
civic number)
Statistics
Disit
•
•
•
•
•
•
•
•
•
Bar content
Column content
Gauge chart
Generic content
Time trend compare
Pie chart
Single content
Speedometer
Time trend
Service_Active_FI
Number of active serrvices
in Florence
Statistics
Disit
•
•
•
•
•
•
Bar content
Column content
Gauge chart
Generic content
Time trend compare
Single content
41
Dashboard Management System
Name
Description
Area
Source
Widget type
•
•
Speedometer
Time trend
SmartDS_Process
Result of a project on the
martDS tool
Statistics
Disit- SmartDS
•
•
Pie chart
SmartDS
Temperatures
Fake metric simulating
temperature statistics
Fake area
Disit
•
•
•
•
•
•
Radar series
Pie chart
Table
Line series
Curved line series
Bar series
Tourists
Fake metric simulating
tourists flow
Fake area
Disit
•
•
•
•
•
•
Radar series
Pie chart
Table
Line series
Curved line series
Bar series
TweetsRet_Florence_Day
Number of tweet/retweets Social network Disit- Twitter
on the Florence channel per
Vigilance
day
•
•
•
•
•
•
•
•
Bar content
Column content
Gauge chart
Generic content
Time trend compare
Single content
Speedometer
Time trend
UrbanFaults
Fake metric simulating
urban faults data
Fake area
Disit
•
•
•
•
•
•
Radar series
Pie chart
Table
Line series
Curved line series
Bar series
WeatherStations
Fake metric simulating
weather stations data
Fake area
Disit
•
•
•
•
•
•
Radar series
Pie chart
Table
Line series
Curved line series
Bar series
WifiStream_Aps
Number of active Access
Wi-Fi Points in Florence
active in the last 5 mins.
Network
Disit
•
•
•
•
•
•
•
•
Bar content
Column content
Gauge chart
Generic content
Time trend compare
Single content
Speedometer
Time trend
42
Dashboard Management System
Name
Description
Area
Source
Widget type
WifiStream_Events
Number of events in the
Firenze Wi-Fi in the last 5
mins.
Network
Disit
•
•
•
•
•
•
•
•
Bar content
Column content
Gauge chart
Generic content
Time trend compare
Single content
Speedometer
Time trend
WifiStream_Users
Number of Firenze Wi.-Fi
users
Network
Disit
•
•
•
•
•
•
•
•
Bar content
Column content
Gauge chart
Generic content
Time trend compare
Single content
Speedometer
Time trend
Wifi_Conn_Day
* Number of Wi-Fi
connections per day
Network
Disit
•
•
•
•
•
•
•
•
Bar content
Column content
Gauge chart
Generic content
Time trend compare
Single content
Speedometer
Time trend
Wifi_Operative
Percentage of working Wi- Network
Fi access points with respect
to those that should
working in Florence.
Disit
•
•
•
•
•
•
•
•
•
Bar content
Column content
Gauge chart
Generic content
Time trend compare
Pie chart
Single content
Speedometer
Time trend
Wifi_Power_5Ril
Percentage of Firenze Wi-F Network
that provide a value of the
power for at least 5
measures.
Disit
•
•
•
•
•
•
•
•
•
Bar content
Column content
Gauge chart
Generic content
Time trend compare
Pie chart
Single content
Speedometer
Time trend
Wifi_Remark_Day
Number of Firenze Wi-.Fi
events per day
Disit
•
•
•
•
•
•
•
Bar content
Column content
Gauge chart
Generic content
Time trend compare
Single content
Speedometer
Network
43
Dashboard Management System
Name
Description
Area
Source
Widget type
•
44
Time trend
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising