Feature - Dashboards Update (due for r61)

KPI Dashboard

We are replacing our “old” dashboards for something flexible and more useful, we’ll focus on showing KPIs.

In a second phase, we’ll update “Reports” for better graphic libraries that will allow us to do far better job at showing information in “graphical” terms. We like this library for working wiht graphical interfaces: https://d3js.org/

User Dashboard

When the user logs in a personalised set of metrics will be shown to the user based on the role he/she has on each section.

REMBER: “Roles” within each section will be “Customizable” in the future, this means that each section might have in the future more rows than shown here based on what custom fields you will define.

  • Numbers will be links to each section that will show the information using filters.
  • Coming “cell’s” (actions the user must perform in the future) will show items a “week” from now.
  • Numbers will be “stored” every day, because we want to be able to:
  • Download this numbers over time (CSV)
  • Generate graphs over time
  • We want the user to define its own KPI on each section using its “private” filters (not on the first iteration)
  • When workflows come to live, this section will also indicate what “Actions” are missing in terms of workflows (not on the first iteration)
  • A single PDF will be available for download and also sent by email as an “Awareness” notification.

The list of KPI are kept on this spreadsheet: Dashboard - Google Sheets

Admin Dashboard

When a user logs into the system, if it is in a special group (system / settings / groups) of people will be shown an “Admin Dashboard”, the difference with the previous dashboard is that this one shows data no matter if the data is related to the logged user or not. This dashboard will be created once we feel confortable with the “User Dashboard”

  • Each “Section” has a predetermined number of metrics, they are the output of:

  • A filter count (the number of results a filter returns)

  • The summatory of a column of a filter (for example a metric that shows the total risk score of the organisation would sum the “Residual Risk” and show it on the KPI)

  • It will be possible to include on each section two dynamic KPIs

  • Existing filters on each respective section

  • API fed metrics (for example, i’ll fed once a day the KPI using a remote REST API call)

  • Numbers will be “stored” every day, because we want to be able to:

  • Download this numbers over time (CSV)

  • Generate graphs over time

  • Thresholds will be possible to define in order to “colour” metrics based on the “weekly” variance.

  • A single PDF will be available for download and also sent by email as an “Awareness” notification.

The full list of KPI for this dashboard is documented on this google spreadsheet: Dashboard - Google Sheets

Displaying mode

When the user logs in it will be redirected to this dashboard (unless it hit a direct URL) , if the user mets the condition to see one or the another it should somehow be possible to switch from one view to the other.


Got feedback today on linking KPI


i think it would be a shame to remove the calendar view completely, It is a nice illustration of “the year wheel” in terms of audits, controls and reviews, and provides an overview when planning for future GRC activities, perhaps it could be a seperate tab?

Dont worry - we’ll keep it in the end :slight_smile:

Will the updated dashboard - kpi’s be available on the demo site before release ?

We are working on it

we are trying to push the team to get it done by Friday / Saturday , it will be public to everyone as an update!

We are almost there … obviously was far more complicated than we had anticipated it.

We are updating a few things on dashboards which were not working and adding a few functionalities, this will be released on r61 (unless a hotfix is needed)

The admin dashboard will include functionalities to:

  • define thresholds
    • for each metric (on user and admin dashboard) define a minimum and maximum value, a colour to each one of them and a description (that is shown when the mouse is over the KPI)
    • for each metric define a % variation since the last pool, define colour and a message too.
  • download data as csv
    • Current Values
    • Historical Values (the user defines the from and to using a calendar)

The buttons are now:

  • A: Actions
    • Store Current KPI Values Now
    • Recalculate Current KPI Values Now
    • Add KPI from saved Filters
  • B: Settings
    • Define Thresholds
  • C: Download & Store
    • Current Values
    • Historical Values

We need to include two tags

  • Last calculation on 4th May 1:00am localtime
  • Last time we stored values 1st May 1:00am localtime

A few modifications

  • We’ll store KPI metrics (monday and fridays 1am) twice a week or when the user “Clicks”
  • We’ll calculate KPI metrics every day at 1am (as ew do today) or when the user clicks “Update Now”

This is all needed for the new template coming up…so it will be re-adjusted once we publish the new template for sure.

I want to re-focus a question on this “Admin Dashboard” concept. Why must I put a user in the Admin group (today) in order to see that Dashboard? The Admin group provides access to many things not related to the need to see the Dashboard, which some users should not have.

This other thread started with a similar example of the needs to segregate system-level “Admin” from business-level administration of the data and information (where the system Admins are not the business unit owners of the system and the data).

Does the current re-design you’re working on address the need to separate system administration duties from the need to access all data and dashboard information?