Monitoring Module Summary Dashboard
The 'Summary' tab in the Monitoring module contains a dashboard made up of several smaller dashlets that focus on different aspects of the Monitoring module. This dashboard will present two main elements:
Status
The first element is the Summary rating dashlets which cover Monitoring Compliance and Risk. These provide a summary of the current data in the Monitoring module, giving you an insight into the overall performance and potential issues, and additionally outlining if there are any open Monitoring Records in the system that may be increasing the Risk posed to your Site.
Key Data and Trends
The second element you will find is a set of dashlets that present the most important activity data relating to Monitoring Records. For example, you will see in a clear, intuitive and user-friendly way the information on the number of Monitoring Records that are open and overdue.
The 'Open Monitoring Records' dashlet displays an analysis of the total number of open Monitoring Records, along with the total of overdue Records, and overdue Records with a significant Risk. The open Monitoring Records are grouped and displayed by Programme, and clicking on the blue bar will open that Monitoring Programme in a new browser page. Only the top 10 Programmes will be displayed and they will be displayed in descending order.
Image: 'Open Monitoring Records' Dashlet
1. Open Monitoring Records: This is the total number of all open Monitoring Records - these are found in the 'Actions' tab. This includes all open Records, including significant & not significant Risk, as well as overdue Records.
2. Overdue Monitoring Records: This is the number of open Monitoring Records that are overdue (the data does not include archived or deleted Records). Records created via the 'Add Record' option or added directly through a Programme become overdue when they are open 14 days or longer. Records open via a Scheduler become overdue when another Record is triggered and created, but the previous Record has not been completed yet, or when it passes its 'Due Date', whichever date is older.
Click here to learn more about the overdue Records dashlet.
3. Overdue Monitoring Records with Significant Risk: This is the number of open Monitoring Records that are overdue and carry a significant Risk i.e., Medium or High Risk, depending on the Risk Assessment Model used.
4. Open Monitoring Records By Programme: This line graph displays the top 10 Monitoring Programmes from which the open Records were generated and the number of Records that are open for that Programme. Hover over the bar to display the number of open Records or click on the bar to access the Programme and view all of the related open Records via the 'Programme Record' dropdown.
Image: 'Open Monitoring Records by Programme' in Dashlet - Monitoring Programme Access after Clicking the Programme Name on the Bar
The 'Overdue Monitoring Records' dashlet displays an analysis of the total number of open Records that are overdue, and the number of open Records with a significant Risk that are overdue. The overdue Monitoring Records are grouped and displayed by Programme, and clicking on the blue bar will open the source Monitoring Programme in a new browser page. Only the top 10 Programmes will be displayed and they will be listed in descending order.
The overdue Monitoring Records do not include archived or deleted Records - only Records in the 'Actions' tab are considered for this data.
Image: 'Overdue Monitoring Records' Dashlet
1. Overdue Monitoring Records: This is the total number of overdue Monitoring Records (with insignificant and significant Risk).
2. Overdue Monitoring Records with Significant Risk: This is the number of overdue Records with a significant Risk only. If the System Risk Assessment Model is used in the module, Medium and High Risks are considered significant.
3. Overdue Monitoring Records by Programme: This line graph displays the top 10 Monitoring Programmes from which the overdue Records were generated and the number of overdue Records that are open for that source Programme. Hover over the bar to display the number of overdue Records or click on the bar to access the Programme and view all of the related overdue Records via the 'Programme Record' dropdown in the source Monitoring Programme page.
4. Days Overdue: The bottom of the dashlet displays the 'Days Overdue' line graph. This is a colour-coded graph to allow you to quickly see how the overdue Records are spread out in the module. The number of Records overdue by 1-7 days will appear on a grey bar, 8-14 days will appear on a blue bar and 15+ days will appear on an orange bar. The actual number will be displayed within each bar colour for easier viewing.
Different combinations of conditions will cause Monitoring Records to become overdue, such as:
Condition 1. Record opened via Scheduler + Record creation date older than the most recently triggered Record for the Programme = Overdue
Condition 2. Record does not meet Condition 1 + Record without significant Risk + older than 14 days = Overdue
Condition 3. Record does not meet Condition 1 + Record with significant Risk + older than 7 days = Overdue
The 'Monitoring Programmes Compliance' dashlet displays the current compliance rating of the Monitoring module, however, it only takes into consideration the open Records in the module. The aim is 100% Compliance.
Compliance is a measure of all the activities that should be currently completed (overdue open Records). For example, if there are 100 open Monitoring Records in the 'Actions' tab and 50 of those Records are overdue, then you will be operating at a 50% Compliance rating.
Image: 'Monitoring Programmes Compliance' Dashlet - Low (<33%)
Image: 'Monitoring Programmes Compliance' Dashlet - Medium (33% - 66%)
Image: 'Monitoring Programmes Compliance' Dashlet - High (>66%)
Monitoring Programmes Compliance Ratings: Low Current Compliance Rating (red) = <33%; Medium Current Compliance Rating (orange) = 33%-66%; High Current Compliance Rating (green) = >66%.
The 'Monitoring Programmes Risk' dashlet displays the current Risk rating of the Monitoring module, however, it only takes into consideration the open Records with significant Risk in the module. The aim is 0% Risk.
Risk is a measure of all the activities with significant Risk that should be currently completed (overdue significant Risk open Records). For example, if there are 100 open significant Risk Monitoring Records in the 'Actions' tab and 50 of those significant Risk Records are overdue, then you will be operating at a 50% Risk rating.
Image: 'Monitoring Programmes Risk' Dashlet - High (>66%)
Image: 'Monitoring Programmes Risk' Dashlet - Medium (33% - 66%)
Image: 'Monitoring Programmes Risk' Dashlet - Low (<33%)
Monitoring Programmes Risk Ratings: Low Current Risk Status (green) = <33%; Medium Current Risk Status (orange) = 33%-66%; High Current Risk Status (red) = >66%.
The 'Tests Out-of-Specification' dashlet displays the sum of all Tests that are out of specification ('Fail' result) and Tests that are in the warning zone ('Pass, Warning' result). For this dashlet, both types of Records are considered, i.e., Open and Closed Records.
Image: 'Tests Out-of-Specifications' Dashlet
1. Tests Out-of-Specifications: This is the total number of Tests that received a 'Fail' result in all of the Monitoring Records combined.
2. Tests in the Warning Zone: This is the total number of Tests that received a 'Pass, Warning' result in all of the Monitoring Records combined.
The 'Tests Out-of-Control (SPC)' dashlet displays the sum of all Tests where the latest SPC Result is equal to 0 (out-of-control). For this dashlet, both types of Records are considered, i.e., Open and Closed Records.
Image: 'Tests Out-of-Control (SPC)' Dashlet
1. Tests Out-of-Control: This is the total number of Tests Out-of-Control for all of the Monitoring Records combined. The Out-of-Control Tests are based on the Statistical Process Control (SPC) rules set up. Click here to learn more about setting up SPC for the Monitoring module.
This dashlet displays an outlook on the completed Monitoring Tests in the last 12 months and analyses the 'Fail' results.
Image: 'Monitoring Tests by Result' Dashlet
1. Total Monitoring Tests Completed in the Last 12 Months: This is the total number of completed Tests in the Monitoring module in the last 12 months.
2. Total Monitoring Tests Failed in the Last 12 Months: This is the total number of completed Tests in the Monitoring module that have failed in the last 12 months.
3. Monitoring Tests Failure Rate in the Last 12 Months: This shows the percentage of failures, calculated by dividing the Failed Completed Tests (2) by the Total Completed Tests (1).
4. Monitoring Tests Failure by Week: This chart displays the total number of all failed Tests by week of the year. Only completed actions are considered. You can hover over the plotted points to see the exact quantity of failed Tests for that week.
5. Failed Monitoring Tests by Programme: This chart displays in descending order the top 10 Programmes that received the most 'Fail' Results for Monitoring Tests. Only completed actions are considered. Clicking on the bar next to the name of the Programme will bring you directly to the Monitoring Programme for which the tests have failed.
A completed action means the 'Monitoring Record' stage has been 'Saved & Submitted' in the Monitoring Record, i.e., the Test results have been confirmed. This does not necessarily mean that the full Monitoring Record is completed and closed.
The 'Monitoring Tests Volume' dashlet displays the total number of Tests generated in the Monitoring module in the past 12 months. It captures the Tests used for all completed actions for the Monitoring Records and the data is grouped by year and month of the year.
Image: 'Monitoring Tests Volume' Dashlet
1. Monitoring Tests Created in the Last 12 Months: This is the total number of Monitoring Tests generated in the last 12 months. This includes Tests in open Records (if the 'Monitoring Record' stage has been 'Saved & Submitted') and closed Records.
2. Significant Monitoring Tests Created in the Last 12 Months: This shows how many Tests from the total of the Monitoring Tests created in the last 12 months have been identified as having significant Risk.
3. Total Tests Created in the Last 12 Months: The graph displays the number of Monitoring Records created by month for the past 12 months. You can hover over the points on the graph to see the exact quantity created for that month. If you were to add all of the figures for each of the points, the total figure would be equal to the figure displayed in point (1).
Note: The Monitoring Tests refer to the Tests added to Monitoring Programmes and the Monitoring Test quantities are sourced from the Monitoring Records.
The significant Monitoring Tests are Tests used in Records that carry a significant Risk.
This dashlet displays an analysis of the total number of open Monitoring Records by their Record workflow stage as a percentage of the overall open Records.
Image: 'Open Monitoring Records by Stage' Dashlet
1. Stages: Monitoring Records are broken into workflow stages. Each open workflow stage is highlighted in a distinct colour: blue, orange, grey and brown.
2. Percentage of Open Monitoring Records by Workflow Stage: The pie chart shows the total number of open Monitoring Records in the center and the percentage of Records in each open workflow stage. Hovering on any colour on the chart will show you the % of Records in that workflow stage.
The chart shows the percentage of open Monitoring Records that are in each workflow stage. In the above example, 59% of open records are in the 'Monitoring Record' workflow stage, and 11% of open Monitoring Records are in the 'Retest' workflow stage.
Tip: In some cases the percentage may be cut off in the image, but hovering over the required area will show you the percentage.
In the above example, you can see that only '5...' is visible, but hovering over the section reveals the full percentage figure of '59%'.
The 'Monitoring Programme Alerts' dashlet displays an analysis of the Alerts that have been triggered in the last 24 hours from the Monitoring module. Only the Alerts set up in the Alerts module are considered here. The dashlet also displays the Alert quantity by time of the day as well as a list of the top 10 most recent Records for which an Alert has been fired.
Image: 'Monitoring Programme Alerts' Dashlet - Activity Noted in the Last 24 Hours
1. Significant Risk Monitoring Programme Alerts in the Last 24 Hours: This is the total number of Alerts fired in the last 24 hours for Monitoring Programmes with significant Risk.
The chart above displays the count of Alerts for Monitoring Programmes with significant Risk created in the last 24 hours, grouped by hour. Hovering over the bar will show you how many Alerts were fired in that specific hour.
2. Monitoring Programme Alerts in the Last 24 Hours: This is the total number of all Monitoring Programme Alerts fired in the last 24 hours and they are grouped by hour - this includes Alerts for Monitoring Programmes with no significant Risk as well as with significant Risk.
The chart above displays the count of Alerts for all Monitoring Programmes created in the last 24 hours, grouped by hour. Hovering over the bar will show you how many Alerts were fired in that specific hour.
3. Recent Alerts: The list of recent Alerts displays the Monitoring Record name in the first column, Alert description in the second column and the date/time when the Alert was triggered in the last column. The Alerts are sorted by creation date, in descending order, and the Records can be accessed by clicking on the name of the Record. An orange name indicates a Monitoring Record with significant Risk, a blue name indicates a Monitoring Record with non-significant Risk.
Recent Alerts include the top 10 most recent Alerts from the last 24 hours for Monitoring Programmes.
If the Monitoring module has not fired any Alerts in the last 24 hours, the dashlet will appear blank.
Image: 'Monitoring Programme Alerts' Dashlet - No Activity Noted in the Last 24 Hours
This dashlet displays an analysis of the overall volume of activity in the Monitoring module based on the number of actions completed. A completed action means a workflow stage has been 'Saved & Submitted' and a signature was provided for the workflow stage.
Image: 'Recent Monitoring Activities' Dashlet
1. Monitoring Actions Completed in the Last 7 Days: This is the total number of Completed Monitoring Actions ('Saved & Submitted' Workflow Stages) for Monitoring Records in the last 7 days.
2. Significant Monitoring Actions Completed in the Last 7 Days: This is the total number of Completed Monitoring Actions ('Saved & Submitted' Workflow Stages) for Monitoring Records with Significant Risk in the last 7 days.
3. Volume of Monitoring Records by Week: This graph displays the count of Completed Monitoring Actions ('Saved & Submitted' Workflow Stages) in the last 12 weeks (84 days), grouped by the week of the year. Hover over a plotted point to see the exact number of Actions.
4. Recent Actions: This list of Recent Actions displays the 10 most recent Monitoring Records in which a workflow stage has been 'Saved & Submitted' by Users in the last 7 days. The recent actions are ordered by module (Monitoring), Record name and date of last activity - sorted in descending order by Date. The Records can be accessed by clicking on the orange or blue 'Monitoring' title for the required Monitoring Record. An orange name indicates a Monitoring Record with significant Risk, a blue name indicates a Monitoring Record with non-significant Risk.
In the 'Summary' Dashboard, for the relevant dashlets, a Monitoring Action or a Completed Action refers to a workflow stage that has been 'Saved & Submitted'. This is to allow open Monitoring Records to be considered for the data in the dashlets.
