DCM Reports and Dashboards
This page lists and describes all reports included in the DCM application. Most of the reports are included in different dashboards.
These reports and dashboards are provided as examples. It's highly recommended to create your own dashboards by taking a copy and selecting the reports you would like to use. So, always make a copy of the original report first so that you don't lose any changes includes in the future DCM versions.
Current list is based on DCM version 5.1.1.
Dashboards
DCM includes several dashboards for different audiences and perspectives. More information about the dashboards included in different DCM versions can be found via the links below:
DCM 5.1.1: Split the "Data Quality Overview" dashboard into Weekly and Monthly views
DCM 5.1: Added more interactive filters
DCM 5.0: First DCM version with interactive dashboards
Reports
The following reports are included in the DCM application. Please note that not all of these are included in a dashboard, but can be used via Reports View/Run list or by adding to your own dashboards.
NEW | Indicates that the report has been added in the last couple of releases. |
IN USE | Means that report is valid and can be used as described. Note that not all reports "In use" are included in default dashboards, but these are worth checking when creating new dashboards and especially before starting to create new reports based on DCM data. |
DEPRECATED | Means that the report is no longer relevant and will be deleted on a later release. These reports also have "(Deprecated)" text in their name. This indicates to DCM customers that these reports can be deleted eventually (when deleted from DCM app also) and should not be used anymore. |
DELETED | Means that system admin should delete that report from the customer instance. Deletions can not be included in scoped applications, so deletions have to be done manually. |
Active reports
Note: All thumbnails may not be up-to-date and this report list is still under construction.
| Report Title (Name, if <> Title) | Thumbnail | Type | Source table | Description | Status | on Dashboard |
|---|---|---|---|---|---|---|---|
1 | Active Task Configurations DCM Tasks - Active Task Configurations | | Single score | x_jugr_dcm_task | Number of currently active task configurations that can create new DCM tasks while audits are being run. Usage: shows if automated task creation is in use and how widely it's used. Also provides access to active task configuration list. | IN USE | Workspace - Overview |
2 | Aging Data Remediation Tasks DCM Tasks - Aging Data Remediation Task | | Bar | x_jugr_dcm_task | Open data remediation tasks based on their creation date. Usage: Left side of the report shows how many new tasks are getting created while the right side shows if these tasks are getting completed or not. High bars on the right side means that the process does not work properly. | IN USE
| Workspace - Overview |
3 | My Aging Data Remediation Tasks DCM Tasks - My Domains - Aging Data Remediation Task |
| Bar | x_jugr_dcm_task | Same as "Aging Data Remediation Tasks", but filtered based on Data Domains related to current user. | IN USE | Audit - My Data Domains |
4 | DCM - Audited fields per Field Setup DCM - Audited fields per Field Setup | | List | x_jugr_dcm_... field_condition | List of field names and their conditions that are included in different Field setups. Usage: For documentation purposes. | IN USE | Blueprints - Overview |
5 | DCM - Field Setups per Blueprint version DCM - Field Setups per Blueprint version | | List | x_jugr_dcm_m2m_... field_setup_container | Blueprint version list grouped by Field Setups used on those blueprints. Field Setups are common definitions and can be used by multiple blueprint versions. Usage: Identify how different Field Setups are used on different Blueprint versions. | IN USE | Blueprints - Overview |
6 | Bad data removed by Fixed DCM Tasks DCM Tasks - Bad data removed by Fixed DCM Tasks | | Trend | x_jugr_dcm_task | Total weight on completed DCM Tasks as a weekly trend. | IN USE | NO |
7 | Bad data removed by my fixed tasks DCM Tasks - Bad data removed by my fixed tasks | | Single score | x_jugr_dcm_task | Total weight on all completed DCM tasks assigned to the current user. Usage: shows how much the current user has been able to fix issues based on completed DCM tasks. | IN USE | Workspace - My Tasks |
8 | Completed Data Remediation Tasks DCM Tasks - Completed Data Remediation Tasks | | Trend | x_jugr_dcm_task | Number of DCM tasks completed as a weekly trend. Default grouping is by Data Domain. Usage: showing the remediation activities in different domains. | IN USE | Workspace - Overview |
9 | Data Tier Compliance (last 30 days) DCM - Data Tier Compliance (last 30 days) |
| Multilevel pivot | x_jugr_dcm_... audit_instance | Average data compliance per data domain and data tier for the last 30 days shown as a multilevel pivot table. Columns are showing the Implementation phase of the blueprint version. If audits are run once per week, this should show the current situation. If audits are running more often than once a week, then the report is showing avg compliance for the last 7 days. Usage: Shows the "current state" for data quality in different domains. | NEW New in R5.1.1 | Audit - Data Quality - Monthly Overview |
10 | Data Tier Compliance (last 7 days) DCM - Data Tier Compliance (last 7 days) | | Multilevel pivot | x_jugr_dcm_... audit_instance | Average data compliance per data domain and data tier for the last 7 days shown as a multilevel pivot table. Columns are showing the Implementation phase of the blueprint version. If audits are run once per week, this should show the current situation. If audits are running more often than once a week, then the report is showing avg compliance for the last 7 days. Usage: Shows the "current state" for data quality in different domains. | IN USE
| Audit - Data Quality - Weekly Overview |
11 | My Data Domain Compliance (last 7 days) DCM - My Domains - Data Domain Compliance (last 7 days) |
| Multilevel pivot | x_jugr_dcm_... audit_instance | Same as "Data Domain Compliance (last 7 days)", but filtered based on Data Domains related to current user. Usage: See latest audit results and access the more detailed results by clicking a number an opening an Audit Instance into the Audit Results view. | IN USE | Audit - My Data Domains |
12 | Audited records - Weekly trend DCM - Audited records per result type weekly trend | | Trend | x_jugr_dcm_... audit_instance_metric | Total number of audited records (root records) per week grouped by the audit result type. Audited record is only compliant when the record is 100% compliant with the blueprint. Usage: Compared to a blueprint compliance trend that is showing percentages, this one will show the "audit volumes" per week. | IN USE | Audit - Data Quality - Weekly Overview |
13 | Audited records - Monthly trend DCM - Audited records per result type monthly trend | | Trend | x_jugr_dcm_... audit_instance_metric | Total number of audited records (root records) per month grouped by the audit result type. Audited record is only compliant when the record is 100% compliant with the blueprint. Usage: Compared to a blueprint compliance trend that is showing percentages, this one will show the "audit volumes" per month. | NEW New in R5.1.1 | Audit - Data Quality - Monthly Overview |
14 | My Domains Audited records - Weekly trend DCM - My Domains - Audited Records - Weekly trend | | Trend | x_jugr_dcm_... audit_instance_metric | Same as "Audited record - Weekly trend" but filtered based on data domains related to current used. | IN USE | Audit - My Data Domains |
15 | Data Compliance - Weekly Trend DCM - Blueprint compliance per audit messages % average weekly trend | | Spline | x_jugr_dcm_... audit_instance | Data compliance trend based on audit messages as a weekly trend. Average means that if the same audit has been run multiple times during the week, then an average result is shown. Default grouping per Data Tier. Each audited record will generate multiple audit messages, so this trend should show more positive values than the other trend report that is based on audited record compliance. Trend timeline should be selected based on audit schedule or when the results are being reviewed (weekly or monthly for example).
| IN USE Renamed in R4.5 | Audit - Data Quality - Weekly Overview |
16 | Data Compliance - Monthly Trend DCM - Blueprint compliance per audit messages % average monthly trend |
| Spline | x_jugr_dcm_... audit_instance | Data compliance trend based on audit messages as a monthly trend. Average means that if the same audit has been run multiple times during the month, then an average result is shown. Default grouping per Data Tier. Each audited record will generate multiple audit messages, so this trend should show more positive values than the other trend report that is based on audited record compliance. Trend timeline should be selected based on audit schedule or when the results are being reviewed (weekly or monthly for example). | NEW New in R5.1.1 | Audit - Data Quality - Monthly Overview |
17 | Data Compliance - Weekly Trend DCM - Data Compliance - Weekly Trend based on Audit Results |
| Spline | x_jugr_dcm_... audit_results | Basically the same report as "Data Compliance - Weekly Trend" created based on Audit Instances table, but this one is based on Audit Results table. This version of the report allows us to use Interactive Filters related to Audit Results like Data Providers, but this is slower to generate. In instances where number of Audit Results is very high, it's recommended to use the Audit Instance based version of the report. | IN USE
| Audit - My Data Domains |
18 | My Data Compliance - Weekly Trend DCM - My Domains - Blueprint compliance per audit messages % average weekly trend |
| Spline | x_jugr_dcm_... audit_results | Same as "Data Compliance - Weekly Trend", but filtered based on Data Domains related to current user. This report is based on Audit Results, so it provides easy access to more detailed audit results and messages. Usage: See data compliance trends in more detail on areas that you are responsible for (or otherwise related to). No need to create separate reports per domain, when you can simply relate users to different domains. | IN USE
| NO |
19 | My CMDB Data Compliance - CI Attribute Grouping - Weekly Trend DCM - My Domains - Blueprint compliance weekly trend - CMDB CI Groupings | | Spline | x_jugr_dcm_... audit_result_to_root | Same as "My Data Compliance - Weekly Trend", but based on Database View that joins Audit Results with Configuration Items. Filtered based on Data Domains related to current user. Usage: this report provides additional grouping and filtering capability using attributes available on the Configuration Item (cmdb_ci) table. This report only includes Audit Results where the Root Class is inherited from the Configuration Item table. | NEW New in R5.1.1 | NO |
20 | DCM - Data Domain Status DCM - Data Domain Status | | Multilevel pivot | x_jugr_dcm_... data_domain_blueprints | This table is showing status for different data domains. Each domain will have a minimum count 1, but of domain already has blueprints defined those will increase the count. The purpose of this report is to work as a planning and scoping tool for data domains. | IN USE | Blueprints - Overview |
21 | Deviations per Blueprint last month DCM - Deviations per Blueprint last month | | Heatmap | x_jugr_dcm_audit_results | The number of deviations on different levels per blueprint for the last month. | IN USE | NO |
22 | Deviations per Blueprint this month DCM - Deviations per Blueprint this month | | Heatmap | x_jugr_dcm_audit_results | The number of deviations on different levels per blueprint for the current month. This report drills down to table level and then further down to blueprint based trend graph for the month. | IN USE | NO |
23 | Deviations per domain last month DCM - Deviations per domain last month | | Heatmap | x_jugr_dcm_audit_results | The number of deviations on different levels per data domain for the previous month. This report drills down to table level and then further down to blueprint based trend graph for the month. | IN USE | NO |
24 | Deviations per domain this month DCM - Deviations per domain this month | | Heatmap | x_jugr_dcm_audit_results | The number of deviations on different levels per data domain for the current month. This report drills down to table level and then further down to blueprint based trend graph for the month. | IN USE | NO |
25 | New Non-Compliant Unique Audit Messages - Grouped DCM - New Non-Compliant Unique Audit Messages - Grouped | | Horizontal bar | x_jugr_dcm_... unique_audit_message | Non-compliant unique audit messages created within the last 30 days grouped by Audit result type. Other grouping options include deviation level, blueprint element, class, real record, audited record and status. | IN USE | NO |
26 | Non-Compliant Unique Audit Messages per CI Managed by DCM - Unique Audit Messages per CI Managed by | | Horizontal bar | x_jugr_uam_to_root | Example report for using the "DCM Unique Audit Message to Root Record" database view that connects Configuration Items as Audited records to Unique Audit Messages. Through this DB View, reports can include common attributes from the Configuration Item table. This report is using the Managed by reference from CI table to group the non-compliant Unique Audit Messages. Usage: Use this report as an example to create your own reports that would combine CI Attributes and UAM data. | IN USE | NO |
27 | Non-Compliant Unique Audit Messages - Grouped DCM - Non-Compliant Unique Audit Messages - Grouped | | Horizontal bar | x_jugr_dcm_... unique_audit_message | Non-compliant unique audit messages from the last 6 months grouped by the audit result type. Other grouping options include blueprint element, class, real record, audited record and status for example. | IN USE | NO |
28 | Non-Compliant Unique Audit Messages in CMDB - Grouped DCM - Non-Compliant Unique Audit Messages in CMDB - Grouped | | Horizontal bar | x_jugr_dcm_... uam_to_real_records | Non-compliant unique audit messages from the last 3 months grouped by the Managed by field on the Real record related to the unique audit message. This is an example report that uses a database view that connects audit messages into configuration items. This DB view allows using CI attributes as grouping factors. Usage: Use this report as an example to create your own reports that would combine CI Attributes and UAM data. | IN USE | NO |
29 | Non-Compliant Unique Audit Messages per Class DCM - Non-Compliant Unique Audit Messages per Class | | Heatmap | x_jugr_dcm_... unique_audit_message |