Discovery
Application Data Quality
Measure and improve the completeness of application records — identify missing mandatory and suggested fields before they become blockers.
Overview
Application Data Quality scores every application record against a set of mandatory and suggested fields. Each application receives a quality score from 0–100% and is placed into a tier (Excellent, Good, Fair, or Poor). The dashboard helps you prioritise which applications need data entry work before migration planning can begin.
This screen is visible to Administrators only. Project managers should work with an administrator to review and act on quality scores.
When to Use
- After an initial CSV import or integration sync, to measure data completeness
- Before migration planning begins — poor quality data leads to incorrect move groups
- As part of a weekly data governance review to track improvement over time
- When onboarding a new business unit's applications to the CMDB
Dashboard Sections
| Section | What it shows |
|---|---|
| KPI Cards | Total applications, overall quality score (0–100%), count of applications with all mandatory fields complete, count missing critical data. |
| Quality Distribution Chart | Applications grouped into Excellent (≥90%), Good (70–89%), Fair (50–69%), Poor (<50%) tiers. |
| Most Common Missing Fields | Top 5 fields most often left blank across all applications — focus your data entry effort here. |
| Field Completion Rates | Bar chart showing the % completion rate for every tracked field. Mandatory fields shown in dark, suggested in light. |
| Application Quality Details Table | Per-application row: Name, Quality Score, Quality Tier, Missing Mandatory Fields, Missing Suggested Fields, Environment, Business Unit. |
How to Use
1
Navigate to Discovery → Data Quality & Discovery → Application Data Quality.
2
Check the overall quality score KPI. Anything below 70% indicates significant data gaps that should be resolved before planning.
3
Review the Most Common Missing Fields panel. These are the highest-impact fields to fix. Contact application owners to fill in the gaps.
4
Sort the Application Quality Details table by Quality Score ascending to see the poorest-quality records first. Export this list and assign remediation tasks in Governance → Actions.
5
After updating records, return to this dashboard and refresh to see the improved score.
Key Fields
| Field | Description |
|---|---|
| Quality Score | 0–100% score calculated from mandatory and suggested field completeness. |
| Quality Tier | Excellent (≥90%), Good (70–89%), Fair (50–69%), Poor (<50%). |
| Missing Mandatory Fields | Count of required fields with no value — these must be completed. |
| Missing Suggested Fields | Count of recommended fields with no value — completing these improves the score. |
| Environment | Production, Development, Test, UAT, etc. |
| Business Unit | The organisational owner of the application. |
Quality Tiers
| Tier | Score | Meaning |
|---|---|---|
| Excellent | ≥ 90% | Record is fully complete. Ready for migration planning. |
| Good | 70–89% | Minor gaps. Can be used in planning but some fields should be completed. |
| Fair | 50–69% | Significant gaps. Requires data entry before reliable planning. |
| Poor | < 50% | Record is incomplete. Must not be used for migration planning until improved. |
Tips & Common Mistakes
Set a project quality target (e.g. all in-scope applications must reach Good or above) and track it week-on-week using the overall score KPI.
Use Governance → Actions to assign data remediation tasks to application owners with a due date. Link the action to the specific application record.
Mandatory fields are defined in Settings → CMDB Field Management. If the scoring seems wrong, check that mandatory fields are configured correctly for your project.