The next section explains how to use the Analytics module as part of the IriusRisk Analytics module solution.
By default, a set of dashboards will be included and shared with the users in order to have first insights and reporting for IriusRisk data exploitation.
These dashboards belong to an admin user called
defaultIriusRisk and all the content is shared with a
DeaultIriusRisk group. Therefore, every single user that wants to see the dashboards has to belong to this group.
Sign In to Analytics Module
In order to have access to the Analytics module, our Customer Success team will contact you to discuss adding this module to your current IriusRisk license.
For further information about how to request access, please see the following article: Accessing the Advanced Analytics Module
Once the environment is ready, the user will be shown the dashboard panel:
Working with Analytics module elements
Basically, three main elements that we have to deal with are:
Once we have a connection defined (aka datasources) it is possible to create queries in order to obtain all the data needed to be included in our reports:
Creating a new query is as simple as visiting the Query menu option:
With the query results, it is time to create a widget that will form the dashboards.
As soon we have defined a new widget, it is possible to include it as part of dashboards. We can create a new dashboard and include several widgets in it:
It is important to mention that the default dashboards provided can be updated over time, so it is good practice to not modify them, cloning the original ones instead. Otherwise, changes made to default dashboards might be lost.
By default, IriusRisk has deployed a set of dashboards that exploit the IriusRisk database:
These dashboards can be grouped into two categories:
Main dashboard: dashboards that are self info contained (they do not depend on passed filters):
Child Dashboards: those that depend on other dashboards and are filtered by the information provided from the main dashboard.
Portfolio Control Detail
Below, it is possible to see a conceptual map of the different dashboards with their widgets and dependencies between them:
The next example shows how we navigate from the root dashboard Risk Overview to the embedded dashboards Developer Dashboard and Compliance Dashboard
Working with predefined queries
The customer does not need to know anything about the IriusRisk operational data scheme to extract knowledge. We need to hide the complexity of our relational database by creating intermediate queries that can be reused to create a wide variety of self-service widgets.
Article is closed for comments.